summaryrefslogtreecommitdiff
path: root/docsite
diff options
context:
space:
mode:
authorAlexander Ershov <codumentary.com@gmail.com>2014-11-06 13:50:36 +0300
committerAlexander Ershov <codumentary.com@gmail.com>2014-11-06 13:50:36 +0300
commit9112f650c085169bef9ecb17ddaf287a601079cd (patch)
tree98ec34cf883cd699748d8564055b04c6bd365953 /docsite
parent229d49fe36a03d077cc9276e19d4acb9b5965e97 (diff)
downloadansible-9112f650c085169bef9ecb17ddaf287a601079cd.tar.gz
Fix path to the integration tests
"tests/integration" -> "test/integration"
Diffstat (limited to 'docsite')
-rw-r--r--docsite/rst/community.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docsite/rst/community.rst b/docsite/rst/community.rst
index b89d6e61df..d16070239e 100644
--- a/docsite/rst/community.rst
+++ b/docsite/rst/community.rst
@@ -146,7 +146,7 @@ to modify a pull request later.
When submitting patches, be sure to run the unit tests first “make tests” and always use
“git rebase” vs “git merge” (aliasing git pull to git pull --rebase is a great idea) to
-avoid merge commits in your submissions. There are also integration tests that can be run in the "tests/integration" directory.
+avoid merge commits in your submissions. There are also integration tests that can be run in the "test/integration" directory.
In order to keep the history clean and better audit incoming code, we will require resubmission of pull requests that contain merge commits. Use "git pull --rebase" vs "git pull" and "git rebase" vs "git merge". Also be sure to use topic branches to keep your additions on different branches, such that they won't pick up stray commits later.