Commit 2c05bd72c8
Verified · cmc
Layout: unified · split
Users.org +8 −4
| @@ -346,10 +346,14 @@ Semantics worth knowing: | ||
| 346 | 346 | Repo admins can gate merges (=repo settings ...=): =require-approvals |
| 347 | 347 | <n>= (fresh, non-author approvals; each reviewer's latest review is |
| 348 | 348 | their stance, and a fresh request-changes blocks), =require-resolved= |
| 349 | (no open review threads), =require-checks= (all statuses green). With | |
| 350 | approvals required, a =CODEOWNERS= file on the target branch (root or | |
| 351 | =.gitbay/=) additionally demands an approval from an owner of every | |
| 352 | owned changed file — gitignore-style patterns, last match wins. | |
| 349 | (no open review threads), =require-checks= (all statuses green), and | |
| 350 | =require-codeowners= (an approval from an owner of every owned changed | |
| 351 | file). Owners come from a =CODEOWNERS= file on the target branch, root | |
| 352 | or =.gitbay/=, gitignore-style patterns, last match wins. The toggle is | |
| 353 | the opt-in, so a repository can carry the file as documentation of who | |
| 354 | to ask without it gating merges; with it on and no file on the target | |
| 355 | branch, the merge is refused and says so. It does not wait on | |
| 356 | =require-approvals=. | |
| 353 | 357 | |
| 354 | 358 | A merge request whose target is another open merge request's source |
| 355 | 359 | branch is stacked on it: =mr create= says so, =mr show= carries |