Sounds good to me. I merged the PR and re-deployed the api server.
On Mon, Apr 9, 2018 at 5:57 AM, Alexandre Viau <av...@debian.org> wrote:
> Currently, *-guest users in salsa.debian.org/go-team have "Master"
> permissions. I would like to change that to "developer".
> The only group-level permission difference between "Master" and
> "Developer" on gitlab is:
> - "Create project in group" (this is originally why I gave them Master
> Project-level differences include:
> - pushing to protected branches (they need this!)
> - Edit project (and all project settings)
> - *-guests users should use dh-make-golang to create projects. They
> shouldn't require the "create project in group" permission.
> - *-guest users should be able to push to protected branches
> We can allow developers to push to protected branches. This is
> configurable. When you protect a branch, you may allow "developers" to
> push to it.
> I reconfigured all of our protected branches to allow pushes from
> I sent a merge request to go-team/ci to allow developers to push on
> protected branches:
> - https://salsa.debian.org/go-team/ci/merge_requests/1
> This will have the following benefits:
> - *-guest users will no longer be able to **force push** to important
> branches. This will protect our repositories from mass destruction by a
> guest, but they still can work on repositories as usual.
> - *-guest users will now be forced to use dh-make-golang to create
> repositories. This is nice because some of them currently create
> repositories manually without the team-wide config, as they don't know
> our tools very well yet.
> When/if my merge request on go-team/ci is merged, I will change all
> guest users permissions to "developer".
> What do you think?
> cc-ing Michael because he will need to rebuild and deploy the server
> component of dh-make-golang if this goes trough.
> Alexandre Viau
Pkg-go-maintainers mailing list