catch3
Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results.
Clonegit clone https://git.progmasoft.com/catch3
First draft of issue and PR templates.
- Commit
e1dbb7cf644565a92a66ad0be47fc19a60bdc976- Author
- Martin Hořeňovský ·
- Parents
02a69b449f59
Changes
.github/issue_template.md | 29 +++++++++++++++++++++++++++++ .github/pull_request_template.md | 25 +++++++++++++++++++++++++ 2 files changed, 54 insertions(+) diff --git a/.github/issue_template.md b/.github/issue_template.md new file mode 100644 index 00000000..051b5e5f --- /dev/null +++ b/.github/issue_template.md @@ -0,0 +1,29 @@ +## Description +<!-- +If your issue is a bugreport, this means describing what you did, +what did you want to happen and what actually did happen. + +If your issue is a feature request, describe the feature and why do you +want it. +--> + + +### Steps to reproduce +<!-- +This is only relevant for bug reports, but if you do have one, +please provide a minimal set of steps to reproduce the problem. + +Usually this means providing a small and self-contained code using Catch +and specifying compiler flags/tools used if relevant. +--> + + +### Extra information +<!-- +Fill in any extra information that might be important for your issue. + +If your issue is a bugreport, definitely fill out at least the following. +--> +* Catch version: **v42.42.42** +* Operating System: **Joe's discount operating system** +* Compiler+version: **Hidden Dragon v1.2.3** diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 00000000..95e3ccd2 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,25 @@ +<!-- +Please do not submit pull requests changing the `version.hpp` +or the single-include `catch.hpp` file, these are changed +only when a new release is made. +--> + + +## Description +<!-- +Describe the what and the why of your pull request. Remember that these two +are usually a bit different. As an example, if you have made various changes +to decrease the number of new strings allocated, thats what. The why probably +was that you have a large set of tests and found that this speeds them up. +--> + +## GitHub Issues +<!-- +If this PR was motivated by some existing issues, reference them here. + +If it is a simple bug-fix, please also add a line like 'Closes #123' +to your commit message, so that it is automatically closed. +If it is not, don't, as it might take several iterations for a feature +to be done properly. If in doubt, leave it open and reference it in the +PR itself, so that maintainers can decide. +-->