You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-6Lines changed: 5 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -61,16 +61,15 @@ Making Changes
61
61
--------------
62
62
63
63
+ Create a _topic branch_ for your isolated work.
64
-
* Usually you should base your branch on the `master` branch.
65
-
* A good topic branch name can be the JIRA bug id plus a keyword, e.g.`WEAVER-123-InputStream`.
64
+
* Usually you should base your branch from the `master` branch.
65
+
* A good topic branch name can be the JIRA bug id plus a keyword, for example,`WEAVER-123-InputStream`.
66
66
* If you have submitted multiple JIRA issues, try to maintain separate branches and pull requests.
67
67
+ Make commits of logical units.
68
68
* Make sure your commit messages are meaningful and in the proper format. Your commit message should contain the key of the JIRA issue.
69
-
*e.g. `WEAVER-123: Close input stream earlier`
69
+
*For example, `[WEAVER-123] Close input stream earlier`
70
70
+ Respect the original code style:
71
-
+ Only use spaces for indentation.
71
+
+ Only use spaces for indentation; you can check for unnecessary whitespace with `git diff` before committing.
72
72
+ Create minimal diffs - disable _On Save_ actions like _Reformat Source Code_ or _Organize Imports_. If you feel the source code should be reformatted create a separate PR for this change first.
73
-
+ Check for unnecessary whitespace with `git diff` -- check before committing.
74
73
+ Make sure you have added the necessary tests for your changes, typically in `src/test/java`.
75
74
+ Run all the tests with `mvn clean verify` to assure nothing else was accidentally broken.
76
75
@@ -80,7 +79,7 @@ Making Trivial Changes
80
79
The JIRA tickets are used to generate the changelog for the next release.
81
80
82
81
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA.
83
-
In this case, it is appropriate to start the first line of a commit with '(doc)' instead of a ticket number.
82
+
In this case, it is appropriate to start the first line of a commit with '[doc]' or '[javadoc]' instead of a ticket number.
0 commit comments