-
Notifications
You must be signed in to change notification settings - Fork 1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch '3.2' of https://github.com/corydalis10/testssl.sh into …
…corydalis10-3.2
- Loading branch information
Showing
1 changed file
with
10 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,21 +1,16 @@ | ||
|
|
||
| ### Contributions / participation | ||
| ### Contributing / participating | ||
|
|
||
| is always welcome, here @ github or via e-mail. | ||
| Contributing / participating is always welcome! | ||
|
|
||
| Note please the following | ||
| Please note the following: | ||
|
|
||
| * Please read at least the [coding convention](https://github.com/testssl/testssl.sh/Coding_Convention.md). | ||
| * One PR per feature or bug fix or improvement. Please do not mix issues. | ||
| * Document your PR, both in the PR and/or commit message and in the code. | ||
| * Please read at least the [coding convention](https://github.com/testssl/testssl.sh/blob/3.2/Coding_Convention.md). | ||
| * One pull request per feature or bug fix or improvement. Please do not mix issues. | ||
| * Document your pull request, both in the pull request and/or commit message and in the code. | ||
| * Please test your changes thoroughly as reliability is important for this project. You may want to check different servers with different settings. | ||
| * Travis runs automatically when anything is committed/PR'd. You should check any complains from Travis. Beforehand you can check with `prove -v`. | ||
| * 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. | ||
| * If it's a new feature it would need to be documented in the appropriate section in `help()` and in `~/doc/testssl.1.md` | ||
| * GitHub Actions runs automatically when anything is committed. You should check any complains from GitHub Actions. Beforehand you can check with `prove -v`. | ||
| * 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. | ||
| * If it's a new feature, it would need to be documented in the appropriate section in `help()` and in `~/doc/testssl.1.md` | ||
|
|
||
| For questions just open an issue or feel free to send me an e-mail. | ||
|
|
||
| #### Patches via e-mail | ||
|
|
||
| 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 . | ||
| Let me know how you like them to be attributed. | ||
| For the questions, just open an issue. |