Repository protected branch configuration is ignoring specific branch in favor of wildcard, resulting in being unable to push
Summary
We're unable to push or merge requests with Developer permissions to protected branches since last 2 hours on our repositories. Those protected branches are correctly configured as such:
master:
- Allowed to merge: Developer + Maintainer
- Allowed to push: Developer + Maintainer
* wildcard: (This is to not allow creating other branches different to master)
- Allowed to merge: No one
- Allowed to push: No one
We didn't modify our configuration recently, so we think this is a recent regression. Most of the users have Developer roles, but they appear with the not able to merge + push warning triangle. If trying to push from terminal, it fails with this error: remote: GitLab: You are not allowed to push code to protected branches on this project.
Steps to reproduce
- Create a repository with some content
- Configure protected branches as follows:
- Invite some test user with Developer access
- Try to push to master as the test user, it will fail with this error: remote: GitLab: You are not allowed to push code to protected branches on this project.
Merge requests will also fail to allow to merge.
Example Project
Example: https://gitlab.com/main_group2/subgroup1/testingsomepush Kryword user has only developer access. Protected branch configured as in the previous screenshot, it fails to allow pushing to master.
What is the current bug behavior?
Doesn't allow Developer role to push to protected branch marked as Developer + Maintainer if a general wildcard with lower permissions is also set.
What is the expected correct behavior?
Should allow Developer role to push to protected branch marked as Developer + Maintainer if a general wildcard with lower permissions is also set.
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com