On Wed, May 30, 2018 at 5:14 PM, Stuart Young <cef...@gmail.com> wrote:
> On 31 May 2018 at 02:15, Jason Ekstrand <ja...@jlekstrand.net> wrote: > >> Gitlab divides users into three categories per-project: Guests, >> Developers, and Masters. In general, developers and masters will have push >> access. Masters have the ability to add developers to the project. >> Masters will also have the ability to unlock the branch, force-push, and >> then re-lock if needed. >> > > Just wondering if force-pushing like this would be necessary for people > maintaining the stable branches? From what I gather this would probably be > a rare event (and therefore one of the masters could do it on the > maintainers behalf) but I'm not the one doing this sort of stuff on a day > to day basis. > I should have been more specific. The force-push restriction only applies to "protected" branches. We will likely protect master and the stable branches for each release but any staging branches that the maintainers use will not be protected.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
