deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

<sigh> why won't people read just *one* para more...?

Browse source 
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:
Sitaram Chamarty 2012-02-22 06:07:13 +05:30
parent 9dd191ef7f
commit dceb40a104
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/gitolite.conf.mkd
View file

@ -475,15 +475,15 @@ Some usage hints:
### #mergecheck enforcing a no-merges policy
Some people want to enforce a no-merges policy for various reasons. This
behaviour can be enabled by suffixing an "M" to the end of any permission
starting with `RW` (i.e., all of them except `R`). So for instance, `RW`
becomes `RWM`, and `RW+` becomes `RW+M`, etc.
Some people want to enforce a no-merges policy for various reasons. The new
"M" qualifier can be used to specify who is allowed to push merge commits.
This works just like "C" and "D" in the previous section, so **please read
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"
qualifier tied to any access rule, all rules for that repo are subject to
merge checking, and merge commits will only be allowed when the rule has the
"M" qualifier.
The only other thing to remember is that this qualifier, if used, goes at the
end of any permission starting with `RW` (i.e., all of them except `R`). For
example, `RW` becomes `RWM`, `RW+` becomes `RW+M`, `RW+CD` becomes `RW+CDM`.
## summary: permissions