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