Improve the issue reporting process
This commit adds a set of guidelines to report issues. Related to: #4329
This commit is contained in:
4
.github/ISSUE_TEMPLATE/bug_report.md
vendored
4
.github/ISSUE_TEMPLATE/bug_report.md
vendored
@@ -11,7 +11,7 @@ Please do a quick search on Github issues first, there might be already a duplic
|
||||
If the bug is trivial, just go ahead and create the issue. Otherwise, please take a few moments and fill in the following sections:
|
||||
|
||||
**Bug description**
|
||||
A clear and concise description of what the bug is.
|
||||
A clear and concise description of what the bug is about.
|
||||
|
||||
**Environment**
|
||||
Please provide as many details as possible: Spring Batch version, Java version, which database you use if any, etc
|
||||
@@ -23,5 +23,5 @@ Steps to reproduce the issue.
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
**Minimal Complete Reproducible example**
|
||||
Please provide a failing unit test or a [minimal complete example](https://stackoverflow.com/help/minimal-reproducible-example) that reproduces the issue.
|
||||
Please provide a failing test or a [minimal complete verifiable example](https://github.com/spring-projects/spring-batch/blob/main/ISSUE_REPORTING.md) that reproduces the issue.
|
||||
Bug reports that are reproducible will take priority in resolution over reports that are not reproducible.
|
||||
|
||||
Reference in New Issue
Block a user