@@ -169,10 +169,11 @@ PR Review guidelines
169169====================
170170
171171* We run on a 'use your judgement' system (for better or worse) and do
172- not have a strict nose-count rule. If you have a commit bit, then
173- you are trusted to use it and to know when to ask for more review.
172+ not have a strict 'N devs must sign off on' rule. If you have a
173+ commit bit, then you are trusted to use it and to know when to ask
174+ for more review.
174175
175- * Do not self merge with the exception of un-breaking travis .
176+ * Do not self merge, except for 'small' patches to un-break the CI .
176177
177178* Squashing is case-by-case. The balance is between burden on the
178179 contributor, keeping a relatively clean history, and keeping a
@@ -187,10 +188,10 @@ Backports
187188=========
188189
189190
190- When doing back ports please include the branch you backported the
191+ When doing backports please include the branch you backported the
191192commit to along with the SHA in a comment on the original PR.
192193
193- A quick guide to how to back port a merge commit::
194+ A quick guide to how to backport a merge commit::
194195
195196 git remote update
196197 git checkout target_branch
@@ -202,7 +203,9 @@ A quick guide to how to back port a merge commit::
202203 # leave a comment on PR noting sha of the resulting commit
203204 # from the cherry-pick + branch it was moved to
204205
205- here matplotlib is a read-only remote to the matplotlib/matplotlib repo and DANGER in a read/write remote to the matplotlib/matplotlib repo.
206+ here ``matplotlib `` is a read-only remote to the matplotlib/matplotlib
207+ repo and ``DANGER `` is a read/write remote to the matplotlib/matplotlib
208+ repo.
206209
207210These commands work on git 2.7.1.
208211
0 commit comments