Protected main branch

It would be nice to have the option of locking the main branch. Sometimes by mistake, we edit the main branch, and it would be awesome to guarantee that that does not happen, creating conflicts on the actual branches.

Hi everyone! Thanks for your feedback, we will pass it along to our team for consideration!

In the meantime, as a workaround, you can Request branch reviews (=> you do not give edit access to the main file to these users, so that they’d need to request a review and allow someone who does to merge the branch)
You can find more information in this article: Request a branch review and our Guide to branching.

Thank you Celine, we are aware of it and we use branching heavily.
But still, sometimes it happens. You are just having a conversation, explaining something to someone and then you leave the exploration there because you forget…

Hey Neto! Thanks for your feedback, I understand your frustration.
It is a workaround for whose who may be not aware of it. Still, I will make sure to pass along your feedback (to lock main branch) to the team. I can’t guarantee anything on our end, but I can give it some visibility here! 🙂

All this would really need is a warning when you start editing the main file. Once per session or per day would prevent a lot of issues.

We have a similar experience at Flo. We use branching to add version control to our production files. It’s very easy to make a mistake and edit the master file by accident. Unfortunately the solution you proposed @Celine_Figma means that people with view only access on that file cannot merge their own branches which is a blocker for us.

yep, that would work also