Remove branch protection from main for Pontoon
See original GitHub issueThis morning I woke up to about 2k errors in Pontoon from Common Voice (cc @mathjazz)
Feb 01 13:10:29 mozilla-pontoon app/worker.1: Failed to sync locale fr for project common-voice due to commit error: remote: error: GH006: Protected branch update failed for refs/heads/main.
The branch where Pontoon writes localization needs to be open, not protected.
I’ve disabled sync for this project until the issue is resolved.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (5 by maintainers)
Top Results From Across the Web
About protected branches - GitHub Docs
You can protect important branches by setting branch protection rules, which define whether collaborators can delete or force push to the branch and...
Read more >Protected branches - GitLab Docs
Delete a protected branch · On the top bar, select Main menu > Projects and find your project. · On the left sidebar,...
Read more >How to delete the master branch - Kathrin Holzmann - Medium
On the dropdown, choose main instead of master and click update. On the Branch protection rules for master click edit.
Read more >GIT: How to protect the branch from being removed by other ...
There are many ways to tackle this: Make another repo that's a sand box, and give readonly access to the master one. If...
Read more >Tree Removal - National Trust - Scafffloat - Pontoon Hire UK
We built an 8m x 4m ScaffFloat pontoon which the ranger and tree surgeon worked from to trim the tree branches before pulling...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey Zac, most projects use separate -l10n repositories to allow for using protected branches on the main development repositories. Another benefit of such setup is to avoid Pontoon commits from overflowing the commit history.
This is not only needed for Pontoon, but also for the Sentence Collector sentence exports, as well as the string exports: https://github.com/common-voice/sentence-collector/actions/runs/1781954589/attempts/1