summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorMichael DeHaan <michael.dehaan@gmail.com>2013-12-15 11:50:18 -0500
committerMichael DeHaan <michael.dehaan@gmail.com>2013-12-15 11:50:18 -0500
commit7ff430f461f5772f7d559475201279903fc8ba55 (patch)
tree9aa112215723e2c4d362353a99d66ef42d87f15e /README.md
parent49667a40c8b389fe817444f7f2a6e1d6a093459a (diff)
downloadansible-7ff430f461f5772f7d559475201279903fc8ba55.tar.gz
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index c1662f951c..17d0846a3b 100644
--- a/README.md
+++ b/README.md
@@ -27,7 +27,9 @@ Design Principles
Get Involved
============
- * Read [Contributing.md](https://github.com/ansible/ansible/blob/devel/CONTRIBUTING.md) for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
+ * Read [Contributing.md](https://github.com/ansible/ansible/blob/devel/CONTRIBUTING.md) for all kinds of ways to contribute to and interact with the project, including mailing list information and how to submit bug reports and code to Ansible.
+ * When submitting a bug report, include 1) the output of 'ansible --version', 2) what you expected to happen, 3) what actually happened, and 4) any relevant commands and output.
+ * All code submissions are done through pull requests. Take care to make sure no merge commits are in the submission, and use "git rebase" vs "git merge" for this reason. If submitting a large code change (other than modules), it's probably a good idea to join ansible-devel and talk about what you would like to do or add first and to avoid duplicate efforts. This not only helps everyone know what's going on, it also helps save time and effort if we decide some changes are needed.
* irc.freenode.net: #ansible
Branch Info