THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- How to create a patch file:
- The preferred naming convention for Sentry patches is SENTRY
-12345.patch
, or SENTRY-12345.001.patch
where12345
is the JIRA number. You might want to name successive versions of the patch something like SENTRY-12345.002.patch
, SENTRY-12345.003.patch
, etc. as you iterate on your changes based on review feedback and re-submit them. - If the patch is targeted for other branch, the patch name should be followed by "-" and the branch nameSENTRY-<JIRA number>.<patch version>-<branch name>, for example: SENTRY-12345.001-branch1.patch
The command to generate the patch is "git diff". Example:
Code Block $ git diff > /path/to/SENTRY-1234.001.patch for Branch $ git diff > /path/to/SENTRY-1234.001-branch1.patch
Read the patch file. Make sure it includes ONLY the modifications required to fix a single issue.
- The preferred naming convention for Sentry patches is SENTRY
...