<sigh> why won't people read just *one* para more...?
OK I agree the starting line was *just* misleading enough to give the opposite impression, but still, when the next para starts with "The rules are..." wouldn't you expect people would read *that* too?
This commit is contained in:
parent
9dd191ef7f
commit
dceb40a104
|
@ -475,15 +475,15 @@ Some usage hints:
|
||||||
|
|
||||||
### #mergecheck enforcing a no-merges policy
|
### #mergecheck enforcing a no-merges policy
|
||||||
|
|
||||||
Some people want to enforce a no-merges policy for various reasons. This
|
Some people want to enforce a no-merges policy for various reasons. The new
|
||||||
behaviour can be enabled by suffixing an "M" to the end of any permission
|
"M" qualifier can be used to specify who is allowed to push merge commits.
|
||||||
starting with `RW` (i.e., all of them except `R`). So for instance, `RW`
|
This works just like "C" and "D" in the previous section, so **please read
|
||||||
becomes `RWM`, and `RW+` becomes `RW+M`, etc.
|
that for a more detailed description** and apply the same ideas, (including
|
||||||
|
the `@all` trick!) to "M" for "allow merge commits".
|
||||||
|
|
||||||
The rules are exactly the same as for "C" and "D": once a repo has an "M"
|
The only other thing to remember is that this qualifier, if used, goes at the
|
||||||
qualifier tied to any access rule, all rules for that repo are subject to
|
end of any permission starting with `RW` (i.e., all of them except `R`). For
|
||||||
merge checking, and merge commits will only be allowed when the rule has the
|
example, `RW` becomes `RWM`, `RW+` becomes `RW+M`, `RW+CD` becomes `RW+CDM`.
|
||||||
"M" qualifier.
|
|
||||||
|
|
||||||
## summary: permissions
|
## summary: permissions
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue