Blame .github/pull_request_template.md

rpm-build a7f80b
rpm-build a7f80b
Please do not submit pull requests changing the `version.hpp`
rpm-build a7f80b
or the single-include `catch.hpp` file, these are changed
rpm-build a7f80b
only when a new release is made.
rpm-build a7f80b
rpm-build a7f80b
Before submitting a PR you should probably read the contributor documentation
rpm-build a7f80b
at docs/contributing.md. It will tell you how to properly test your changes.
rpm-build a7f80b
-->
rpm-build a7f80b
rpm-build a7f80b
rpm-build a7f80b
## Description
rpm-build a7f80b
rpm-build a7f80b
Describe the what and the why of your pull request. Remember that these two
rpm-build a7f80b
are usually a bit different. As an example, if you have made various changes
rpm-build a7f80b
to decrease the number of new strings allocated, thats what. The why probably
rpm-build a7f80b
was that you have a large set of tests and found that this speeds them up.
rpm-build a7f80b
-->
rpm-build a7f80b
rpm-build a7f80b
## GitHub Issues
rpm-build a7f80b
rpm-build a7f80b
If this PR was motivated by some existing issues, reference them here.
rpm-build a7f80b
rpm-build a7f80b
If it is a simple bug-fix, please also add a line like 'Closes #123'
rpm-build a7f80b
to your commit message, so that it is automatically closed.
rpm-build a7f80b
If it is not, don't, as it might take several iterations for a feature
rpm-build a7f80b
to be done properly. If in doubt, leave it open and reference it in the
rpm-build a7f80b
PR itself, so that maintainers can decide.
rpm-build a7f80b
-->