-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1327 from yarikoptic/enh-cov-templates
ENH: use codecov + templates for PRs and issues
- Loading branch information
Showing
4 changed files
with
62 additions
and
1 deletion.
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 |
---|---|---|
@@ -0,0 +1,49 @@ | ||
_We will be very grateful, if your problem was described as completely as possible, | ||
enclosing excerpts from logs (if possible within DEBUG mode, if no errors evident | ||
within INFO mode), and configuration in particular of effected relevant settings | ||
(e.g., with ` fail2ban-client -d | grep 'affected-jail-name' ` for a particular | ||
jail troubleshooting). | ||
Thank you in advance for the details, because such issues like "It does not work" | ||
alone could not help to resolve anything! | ||
Thanks! (remove this paragraph and other comments upon reading)_ | ||
|
||
### Environment: | ||
|
||
_Fill out and check (`[x]`) the boxes which apply. If your Fail2Ban version is outdated, | ||
and you can't verify that the issue persists in the recent release, better seek support | ||
from the distribution you obtained Fail2Ban from_ | ||
|
||
- Fail2Ban version (including any possible distribution suffixes): | ||
- OS, including release name/version: | ||
- [ ] Fail2Ban installed via OS/distribution mechanisms | ||
- [ ] You have not applied any additional foreign patches to the codebase | ||
- [ ] Some customizations were done to the configuration (provide details below is so) | ||
|
||
### The issue: | ||
|
||
_Summary here_ | ||
|
||
#### Steps to reproduce | ||
|
||
#### Expected behavior | ||
|
||
#### Observed behavior | ||
|
||
#### Any additional information | ||
|
||
### Configuration, dump and another helpful excerpts | ||
|
||
#### Any customizations done to /etc/fail2ban/ configuration | ||
``` | ||
``` | ||
|
||
#### Relevant parts of /var/log/fail2ban.log file: | ||
_preferably obtained while running fail2ban with `loglevel = 4`_ | ||
|
||
``` | ||
``` | ||
|
||
#### Relevant lines from monitored log files in question: | ||
|
||
``` | ||
``` |
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 |
---|---|---|
@@ -0,0 +1,9 @@ | ||
Before submitting your PR, please review the following checklist: | ||
|
||
- [ ] **CONSIDER adding a unit test** if your PR resolves an issue | ||
- [ ] **LIST ISSUES** this PR resolves | ||
- [ ] **MAKE SURE** this PR doesn't break existing tests | ||
- [ ] **KEEP PR small** so it could be easily reviewed. | ||
- [ ] **AVOID** making unnecessary stylistic changes in unrelated code | ||
- [ ] **ACCOMPANY** each new `failregex` for filter `X` with sample log lines | ||
within `fail2ban/tests/files/logs/X` file |
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
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