Love the fact that I can branch on a file. Only wish I could lock the main “prod” file (esp to a library) so that all editors must use branches – ultimately keeping autosaves of other team members from effecting other lower branches.
17 Likes
This is so important. Even the design leads often forget that they are on the main file instead of a branch and end up making huge changes to the entire file without realizing.
1 Like
+100 For this!
1 Like
I really need this
1 Like
Hope this feature will be implemented. Having a lot of trouble managing library files because this feature is missing…
Also I’d suggest, in case of trying to merge a branch into main,
admins/file owners should be able to set default reviewers and at least one reviewer which can’t be removed.
Would help a lot to manage component versions, updates, etc. In general, ensuring a good quality of our libraries.
5 Likes
really need this too!!!
2 Likes
This is significantly more important than displaying video in prototypes
3 Likes
Looking for this feature to be added as well!
1 Like
This is really important. Especially since changes are not tracked that well, so if someone changes a component in main I can’t see what specifically was changed. This only works somewhat decently in branches.
1 Like
i run into autosaving issues with other designers. plz add this as top priority
2 Likes
I need this
1 Like
Currently exploring this, as we want to lock a version that we tested in research, and iterate on it in a branch.
1 Like
100% Agree
Master / Branch Management
That is one of the few features I am missing from Sketch/Abstract. The master/branch management was pretty sleek being able to set reviewers and protect the master file. Especially in the design system where changes can affect everybody’s work and progress. It is quite dangerous right now while onboarding new collaborators not fluent in Figma. Locking all layers to be sure the team starts a branch is quite a waste of time.
1 Like
We desperately need this ability to lock a version that will never change (like a snapshot in time) that we can hand off to developers. That way, even if updates are made to components and libraries for Day 2, it won’t affect any of the Day 1 deliverables, that developers are actively working on.
XD does good job with this. When you publish a version, it’s locked in time, and the viewers can explore different views of the file: Overview of all the screens, showing all the flows (important for wireframes), and Prototypes, viewed as individual screens.
If somebody has cracked this problem already, I’d love to hear about it! 
Me: Breathes on the main file.
Branch: “Updates available from main file”.
