|
1 | 1 |
|
2 | | -### Contributions / participation |
| 2 | +### Contributing / participating |
3 | 3 |
|
4 | | -is always welcome, here @ github or via e-mail. |
| 4 | +Contributing / participating is always welcome! |
5 | 5 |
|
6 | | -Note please the following |
| 6 | +Please note the following: |
7 | 7 |
|
8 | | -* Please read at least the [coding convention](https://github.com/testssl/testssl.sh/Coding_Convention.md). |
9 | | -* One PR per feature or bug fix or improvement. Please do not mix issues. |
10 | | -* Document your PR, both in the PR and/or commit message and in the code. |
| 8 | +* Please read at least the [coding convention](https://github.com/testssl/testssl.sh/blob/3.2/Coding_Convention.md). |
| 9 | +* One pull request per feature or bug fix or improvement. Please do not mix issues. |
| 10 | +* Document your pull request, both in the pull request and/or commit message and in the code. |
11 | 11 | * Please test your changes thoroughly as reliability is important for this project. You may want to check different servers with different settings. |
12 | | -* Travis runs automatically when anything is committed/PR'd. You should check any complains from Travis. Beforehand you can check with `prove -v`. |
13 | | -* If it's a new feature please consider writing a unit test for it. You can use e.g. `t/20_baseline_ipv4_http.t` as a template. The general documentation for [Test::More](https://perldoc.perl.org/Test/More.html) is a good start. |
14 | | -* If it's a new feature it would need to be documented in the appropriate section in `help()` and in `~/doc/testssl.1.md` |
| 12 | +* GitHub Actions runs automatically when anything is committed. You should check any complains from GitHub Actions. Beforehand you can check with `prove -v`. |
| 13 | +* If it's a new feature, please consider writing a unit test for it. You can use e.g. `t/20_baseline_ipv4_http.t` as a template. The general documentation for [Test::More](https://perldoc.perl.org/Test/More.html) is a good start. |
| 14 | +* If it's a new feature, it would need to be documented in the appropriate section in `help()` and in `~/doc/testssl.1.md` |
15 | 15 |
|
16 | | -For questions just open an issue or feel free to send me an e-mail. |
17 | | - |
18 | | -#### Patches via e-mail |
19 | | - |
20 | | -Of course it is fine when you want to send in patches to use e-mail. For the address please grep for SWCONTACT in testssl.sh . |
21 | | -Let me know how you like them to be attributed. |
| 16 | +For the questions, just open an issue. |
0 commit comments