Disabling (or tweaking) automatic protection of master

Follow up on https://twitter.com/Adys/status/1113364594062495744

On all my personal repositories and nearly all my organization repositories, coworkers and I all constantly use git push --force-with-lease on master, which the default restricted branch configuration prevents.

This is especially frustrating because in my workflow (and it's not a particularly uncommon workflow), master is the development branch and doesn't benefit from such a restriction; whereas branches such as stable/* would definitely benefit from being protected by default.

I'd really like to be able to either change branch protection to allow force-pushing for users authorized to push (without necessarily weakening the remainder of the protections), or outright disable protection on newly-created repositories.

Related #34155 (closed)

mentioned in issue #60009 (closed)

mentioned in issue #60072 (closed)

@jleclanche The following proposal is about allowing force pushing to protected branches:

• https://gitlab.com/gitlab-org/gitlab-ce/issues/20742

Please could you take a look?

added Create [DEPRECATED] devopscreate repository settings typefeature labels

mentioned in issue #60183 (closed)

marked this issue as related to #20742 (moved)

mentioned in issue #60503 (closed)

marked this issue as a duplicate of #20742 (moved)

closed