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
+8-2
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ meets all requirements outlined in this document.**
43
43
2. Make a [topic branch](https://github.com/dchelimsky/rspec/wiki/Topic-Branches#using-topic-branches-when-contributing-patches)
44
44
and start hacking.
45
45
3. If your branch becomes several commits behind master, be sure to rebase
46
-
to avoid a merge conflict.
46
+
your change *on top* of master to avoid a merge conflict.
47
47
3. Submit a pull-request based off your topic branch, following the patch
48
48
rules below.
49
49
4. If your patch is non-trivial and you haven't submitted a [signed CLA](http://logback.qos.ch/cla.txt),
@@ -92,7 +92,7 @@ meets all requirements outlined in this document.**
92
92
where necessary. Examples where this would be required:
93
93
* adding/removing a configuration flag to `SyslogAppender`
94
94
* adding a new appender to `logback-classic`
95
-
95
+
96
96
# General style notes
97
97
98
98
Please note that most of the formatting rules are provided in
@@ -179,6 +179,12 @@ try {
179
179
*/
180
180
```
181
181
182
+
The following command will automatically apply/update the license-header comments for *all* Java/Groovy files. Since this command touches more than only your modified files, be sure to exclude unrelated files from your PR.
183
+
184
+
```
185
+
mvn -P license license:format
186
+
```
187
+
182
188
**S5.** Add javadoc for public functions (we won't fault you for skipping private
0 commit comments