Inconsistent protected branch depending on fork process
Summary
Depending on how a project is imported/forked master
is inconsistently protected.
Steps to reproduce
master
is protected
- create empty project, push to master
- create empty project, then
Import from existing repository
master
is not protected
- create project using
Import from existing repository
- fork project using
Fork
button
What is the current bug behavior?
The master
branch is inconsistently protected depending on how the project/repo is created.
The documentation says master
is protected by default for all projects. https://docs.gitlab.com/ce/user/project/protected_branches.html
What is the expected correct behavior?
Protect master
by default for forked projects and imported projects.
Original issue description
Projects do not inherit it's branch protection during fork
After forking a project the branches of the fork are all **unprotected**! Neither
- the global default branch protection
- nor an inheritance
was done :( ...
Edited by Douwe Maan