summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorChelsea H. Komlo <chelsea.komlo@gmail.com>2017-06-28 20:36:59 -0400
committerChelsea H. Komlo <chelsea.komlo@gmail.com>2017-06-28 20:40:15 -0400
commit24d29c7ae0c523da7d59495438bbea10114da5e1 (patch)
tree616fca3f5e201e9ccdbc02ac319d78997c3cb698 /doc
parent0f3084c4f2b6018d4f8b5f6d6868c7c3801eb45d (diff)
downloadtor-24d29c7ae0c523da7d59495438bbea10114da5e1.tar.gz
tor-24d29c7ae0c523da7d59495438bbea10114da5e1.zip
make check is required for all code submissions
integration tests should be run for feature changes/major patches
Diffstat (limited to 'doc')
-rw-r--r--doc/HACKING/CodingStandards.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index c7787a72cc..da8ce62f5e 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -6,7 +6,7 @@ tl;dr:
- Run configure with `--enable-fatal-warnings`
- Document your functions
- Write unit tests
- - Run `make test-full` to test against all unit and integration tests.
+ - Run `make check` before submitting a patch
- Run `make distcheck` to ensure the distribution works
- Add a file in `changes` for your branch.
@@ -32,6 +32,11 @@ Did you remember...
- To base your code on the appropriate branch?
- To include a file in the `changes` directory as appropriate?
+If you are submitting a major patch or new feature, or want to in the future...
+
+ - Set up Chutney and Stem, see HACKING/WritingTests.md
+ - Run `make test-full` to test against all unit and integration tests.
+
How we use Git branches
=======================