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
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ First off, thank you for considering contributing to this project. It's people l
8
8
9
9
-**Ensure the bug was not already reported** by searching on GitHub under [Issues section](https://github.com/PetoPetko/Java-SerialX/issues).
10
10
- If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/PetoPetko/Java-SerialX/issues/new).
11
-
- Make sure that the issue contains well enough description and if possible some additional data as well, such as code examples. This can help to better understand the issue or ease the reproduction process.
11
+
- Make sure that the issue contains decent description and if possible some additional data as well, such as code examples. This can help to better understand the issue or ease the reproduction process.
- Make some changes (add something feature, fix some bugs, improve Javadocs...)
25
25
- Go to SerialXTest and run `examples.implementations.GeneralExample`, `examples.implementations.SimpleQuerying` and `examples.implementations.SerializingWithJson` junit tests. Acknowledge that only changes that meet all the tests can be added to the library!
26
26
- If all the tests are green you can `git add .`
27
-
- Commit your changes (`git commit -am 'describe what you have done (adding/fixing/etc something)'`).
27
+
- Commit your changes (`git commit -am 'describe what you have done (adding/fixing/improving/... something)'`).
- Introduce as few boundaries as possible, try making things as universal as possible (do not use final or private if possible).
34
34
- Try for your code to not stick out stylistically ;)
35
35
- Every added feature must have an outreaching purpose, must be tested, and perform reasonably.
36
-
- Make sure to NOT alter any of the tests unless your use case explicitly requires it, in that case make sure to document it!
36
+
- Make sure to NOT alter any of the tests unless your use case explicitly requires it, in that case, make sure to document it!
37
37
- Every added class and method must be documented (/** doc */) and contain @author and @version. Method does not need to have @author, especially @author of the class is the same.
38
38
- Note: Version does not have to be incremented in any way, adding _SNAPSHOT at the end should be sufficient.
0 commit comments