[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New here, NatTable repository push to master

On Sun, Aug 18, 2019 at 09:16:51AM +0200, Geert Stappers wrote:
> On Sat, Aug 17, 2019 at 02:31:45PM +0200, Vincent Prat wrote:
> > Le 17/08/2019 à 13:52, Geert Stappers a écrit :
> > > On Sat, Aug 17, 2019 at 01:34:43PM +0200, Vincent Prat wrote:
> > ...
> >
> > Now I get the following error when I try to push to master:
> > 
> > remote: GitLab: You are not allowed to push code to protected branches
> > on this project.
> > 
> Strange. According https://salsa.debian.org/java-team/nattable/-/project_members?page=3
> has vivi-guest the developer privilege.
> I don't know how to fix this properly.
> Here I need help from a team member.
> > Pushes to other branches work.
> That allows to create a branch like "helpneeded" or "vivimaster".
> And work with that branch for the time being.

Looking at the settings for Protected Branches [1], we have:

> By default, protected branches are designed to:
> * prevent their creation, if not already created, from everybody except Maintainers
> * prevent pushes from everybody except Maintainers
> * prevent anyone from force pushing to the branch
> * prevent anyone from deleting the branch

And for the master branch of nattable, on Maintainers are allowed to
merge and push.

Looking at the hierarchy of user permissions for gitlab [2,3], the issue
is that Developer is not the same as Maintainer, and vivi-guest is
configured as a Developer (as are others).

As Geert suggests, pushing another branch and opening a merge request
should work fine for now.

The team can discuss what the default access level should be.


[1] https://salsa.debian.org/java-team/nattable/-/settings/repository
[2] https://docs.gitlab.com/ee/development/permissions.html#members
[3] https://docs.gitlab.com/ee/user/permissions.html

Attachment: signature.asc
Description: PGP signature

Reply to: