PUSH_AND_REVIEW already sets the precedent for bundled grants.
Add a MAINTAINER bundle covering push + the pull-request create & merge grants, so a trusted contributor is one permission entry instead of three.
Purposefully omitting self certify since that is a bypass of the peer review requirement. Maintainers must still have the two latch access (ROLE + grant) for certifying their own pushes. This is intended for sole maintainers and the goal is to remove those grants when more than 1 maintainer is participating through fogwall, which would relax the permissions needed (and not overly bundle MAINTAIN with a presumed bypass).
SOLE_MAINTAIN may be a consideration but again, it requires a permission change when maintainer pools grow. So we can just leave it out of the bundle.
Depends on the PR grant landing (SCM API proxy, #264).
PUSH_AND_REVIEWalready sets the precedent for bundled grants.Add a
MAINTAINERbundle covering push + the pull-request create & merge grants, so a trusted contributor is one permission entry instead of three.Purposefully omitting self certify since that is a bypass of the peer review requirement. Maintainers must still have the two latch access (ROLE + grant) for certifying their own pushes. This is intended for sole maintainers and the goal is to remove those grants when more than 1 maintainer is participating through fogwall, which would relax the permissions needed (and not overly bundle MAINTAIN with a presumed bypass).
SOLE_MAINTAIN may be a consideration but again, it requires a permission change when maintainer pools grow. So we can just leave it out of the bundle.
Depends on the PR grant landing (SCM API proxy, #264).