diff options
author | onqtam <vik.kirilov@gmail.com> | 2017-04-12 15:03:42 +0300 |
---|---|---|
committer | onqtam <vik.kirilov@gmail.com> | 2017-05-16 00:22:19 +0300 |
commit | a9675f50d94c425376cacd18e9c06499ab06841f (patch) | |
tree | 8ed34f2284a9ed8da4c1fafd499f9e2ad3af2f1a /CONTRIBUTING.md | |
parent | f41e25b4800719fb686124fda33ddd3ef73acaca (diff) |
- added CII badge
- tiny docs update
- removed tests - trying to figure out WHY ON EARTH ONLY GCC 5 COMPLAINS ABOUT A STRICT OVERFLOW WARNING where there shouldn't be any - see this CI build: https://travis-ci.org/onqtam/doctest/builds/221092038
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 915764a4..edbb7f49 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -12,7 +12,7 @@ Consider opening an issue for a discussion before making a pull request to make All pull requests should be made against the ```dev``` branch because the ```master``` is the stable one with the latest release. -If you're going to change something in the library itself - make sure you don't modify ```doctest/doctest.h``` because it's generated from ```doctest/parts/doctest_fwd.h``` and ```doctest/parts/doctest_impl.h``` - they get concatenated by CMake - so make sure you do a CMake build after you modify them so the ```assemble_single_header``` target gets built. +If you're going to change something in the library itself - make sure you don't modify ```doctest/doctest.h``` because it's generated from ```doctest/parts/doctest_fwd.h``` and ```doctest/parts/doctest_impl.h``` - they get concatenated by CMake - so make sure you do a CMake build after you modify them so the ```assemble_single_header``` target gets built. Also take into consideration how the change affects the code coverage - based on the project in ```scripts/code_coverage_source```. Also update any relevant examples in the ```examples``` folder. This framework has some design goals which must be kept. Make sure you have read the [**features and design goals**](features.md) page. |