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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,11 +61,11 @@ Making Changes
61
61
62
62
+ Create a _topic branch_ for your isolated work.
63
63
* Usually you should base your branch from the `master` branch.
64
-
* A good topic branch name can be the JIRA bug ID plus a keyword, for example,`BEANUTILS-123-InputStream`.
64
+
* A good topic branch name can be the JIRA bug ID plus a keyword, e.g.`BEANUTILS-123-InputStream`.
65
65
* If you have submitted multiple JIRA issues, try to maintain separate branches and pull requests.
66
66
+ Make commits of logical units.
67
67
* Make sure your commit messages are meaningful and in the proper format. Your commit message should contain the key of the JIRA issue.
68
-
* For example, `[BEANUTILS-123] Close input stream earlier`
68
+
* For example, `[BEANUTILS-123] Close input stream sooner`
69
69
+ Respect the original code style:
70
70
+ Only use spaces for indentation; you can check for unnecessary whitespace with `git diff` before committing.
71
71
+ 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.
0 commit comments