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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Before making a contribution, please take the following steps:
8
8
1. Check whether there's already an open issue related to your proposed contribution. If there is, join the discussion and propose your contribution there.
9
9
2. If there isn't already a relevant issue, create one, describing your contribution and the problem you're trying to solve.
10
10
3. Respond to any questions or suggestions raised in the issue by other developers.
11
-
4. Fork the project repository and prepare your proposed contribution.
11
+
4. Fork the project repository and prepare your proposed contribution. The contribution must include unit tests to confirm that it behaves as expected.
12
12
5. Submit a pull request.
13
13
14
14
NOTE: All contributors must have a contributor license agreement (CLA) on file with FINOS before their pull requests will be merged. Please review the FINOS [contribution requirements](https://community.finos.org/docs/governance/Software-Projects/contribution-compliance-requirements) and submit (or have your employer submit) the required CLA before submitting a pull request.
<!-- Checkstyle configuration that checks the sun coding conventions from: - the Java Language Specification at http://java.sun.com/docs/books/jls/second_edition/html/index.html
7
-
- the Sun Code Conventions at http://java.sun.com/docs/codeconv/ - the Javadoc guidelines at http://java.sun.com/j2se/javadoc/writingdoccomments/index.html - the
8
-
JDK Api documentation http://java.sun.com/j2se/docs/api/index.html - some best practices Checkstyle is very configurable. Be sure to read the documentation at http://checkstyle.sf.net
9
-
(or in your downloaded distribution). Most Checks are configurable, be sure to consult the documentation. To completely disable a check, just comment it out or delete
10
-
it from the file. Finally, it is worth reading the documentation. -->
11
-
12
6
<modulename="Checker">
13
-
<propertyname="severity"value="warning" />
14
-
<!-- If you set the basedir property below, then all reported file names will be relative to the specified directory. See https://checkstyle.org/5.x/config.html#Checker
0 commit comments