Disable push --force pre-hook in GNOME/
Let's start a discussion about removing the prehooks on disk that we have that prevents git push --force on branches that are not wip/*.
Disavantatges of current approach with disk protection
- GitLab UI and on-disk permissions differ
- When a person with Developer access to a project clicks "create merge request" it creates a branch in the main repository with a name that doesn't start with "wip/", making effectively useless the contribution. Note that this does not happen if you are not developer, since "create merge request" will go to your fork instead.
- Having as core workflow branch handling it feels quite confusing and limiting to prevent the use (effectively) of all branches that doesn't start with wip/*, instead of the opposite of protecting specific branches.
Advantages of using GitLab branches protection
- Everything can be managed in the UI. It has wildcards patterns too.
Needs to be checked
- Does GitLab protection also works for CLI pushes?
- Can we have a set of branches that are protected in all projects in GNOME/ and set them with the migration tool?
- Do we satisfy every reason we had the oposite (everything blocked instead of wip/*) with this approach?
- Do people need to change remote to GitLab one so everything goes through here first? Or doesn't it matter?
Edited by Carlos Soriano