summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2016-08-10 20:55:36 -0700
committerTim Smith <tsmith@chef.io>2016-08-10 20:55:36 -0700
commitb1b295e60e26bb5316b27649348da1b6ba2dc614 (patch)
tree189eae2f0c3d61566cd905e07aba04f97c2acbb2 /CONTRIBUTING.md
parent6474554cf70f17387c5a88be547dade30f3e13ee (diff)
downloadchef-b1b295e60e26bb5316b27649348da1b6ba2dc614.tar.gz
Additional readme updates
Signed-off-by: Tim Smith <tsmith@chef.io>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index edf3e7428d..4f9f527381 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -26,7 +26,7 @@ Chef is built to last. We strive to ensure high quality throughout the Chef expe
The Chef Code Review process happens on Github pull requests. See [this article](https://help.github.com/articles/using-pull-requests) if you're not familiar with Github Pull Requests.
-Once you a pull request, the **Chef Engineering Team** or **Chef Core Committers** will review your code and respond to you with any feedback they might have. The process at this point is as follows:
+Once you open a pull request, the **Chef Engineering Team** or **Chef Core Committers** will review your code and respond to you with any feedback they might have. The process at this point is as follows:
1. 2 thumbs-ups are required from the **Chef Engineering Team** or **Chef Core Committers** for all merges.
2. When ready, your pull request will be tagged with label `Ready For Merge`.