Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Gitlab Gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • External wiki
    • External wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • TPA
  • GitlabGitlab
  • Issues
  • #38

Closed
Open
Created Jun 23, 2020 by Matthew Finkel@sysrqb

Protected Branches are problematic for mirroring

CC: @ahf @gk

With #9 (closed) we got cloning/mirroring between gitolite and gitlab. Ignoring #36 (moved) for now, it seems we have a problem with using protected branches. Specifically, we configured protected branches for '*' and disable merging via the web interface, and 'Maintainers' are allowed push access. This seemed like it was close enough to what we wanted, however we now have another problem.

remote: remote: GitLab: You can only delete protected branches using the web interface.        
remote: To dip.torproject.org:tpo/applications/tor-browser-build
remote:  ! [remote rejected] 20254-update-marsigning-check-sh-to-cope-with-signed-os-x-mar-files (pre-receive hook declined)
remote:  ! [remote rejected] maint-9.5 -> maint-9.5 (pre-receive hook declined)
remote:  ! [remote rejected] refs/merge-requests/2/head (pre-receive hook declined)
remote:  ! [remote rejected] refs/merge-requests/3/head (pre-receive hook declined)
remote:  ! [remote rejected] refs/merge-requests/3/merge (pre-receive hook declined)

Specifically, the description of Protected Branches includes:

  • prevent anyone from deleting the branch
  • prevent anyone from force pushing to the branch

I guess we need a different approach.

Edited Sep 28, 2020 by anarcat
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking