GitLab branch protection is broken
On Tor Browser we protect branches to make only the ones we intend use writable.
So, when we create new branches, we need to add a custom rule based on wildcards to push to them.
I've done it as usual, but today it doesn't work:
git push -u upstream tor-browser-115.1.0esr-13.0-1
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
remote: GitLab: You are not allowed to create protected branches on this project.
To gitlab.torproject.org:tpo/applications/tor-browser.git
! [remote rejected] tor-browser-115.1.0esr-13.0-1 -> tor-browser-115.1.0esr-13.0-1 (pre-receive hook declined)
error: failed to push some refs to 'gitlab.torproject.org:tpo/applications/tor-browser.git'
I have indeed the permissions to write to this branch, since I've created a new rule to allow maintainers to push to *-115.1.0esr-13.0-1
.
Also, a few days ago I read something about caching mechanisms (I think they were for the web interface, though) and after that I had also troubles in selecting the new default branch (I selected it, but it wasn't applied to the main repository page), but I don't know if it's related.