Git Like versioning

Wouldn’t this feature request then be called Git Like versioning?
You already have automated version control, it’s just a very simplified single branch version.

That’s correct: git like versioning. I would say it’s not really a version control right now but just a file history.

Version control is weak in Figma right now. It would be really cool to see Figma integrate with Abstract or create their own robust version management system. When you work at a larger company your design has to be peer-reviewed and there is often back and forth between design, PM, and development. It would be amazing if Figma had a way to view that back and forth as well as some form of “approval management flow.”

My ideal flow:

1. I open my design file on the master “branch”
2. I create a new branch called “new feature”
3. I create new designs and then submit the design for review
4. I can choose who I want to review my “new feature” branch
5. The reviewer can leave comments and I can respond until issues are resolved
6. Reviewer can approve the design
7. I merge the design into the master branch
8. If someone modified the same frames as me a conflict will appear and Figma will provide a way to decide which changes to keep.

+1 That’s a big issue at a larger company or when several designers iterate on the same feature. Version control is also very useful when you have to produce many variations for A/B testing.
It’s just how it is like in real life: you iterate, switch back and forth between multiple ideas and variations of the same design, you test, you adjust one of the versions, test again, add something from another variation, etc. Or you simply have to put that new feature on the shelf and get back to it later because priorities changed.

I’m not sure how ‘dark mode’ as a feature is apparently more important than this ! Please implement some form of version control Figma so we never have to deal with ‘X deleted Y by accident’ again!

Ditto, just change your canvas color people!

Right? Let’s vote this topic up!

I thought I was alone thinking this. This and many other suggestions such as layers search, for example, are far more important than dark mode. D:

Yeah, we need the ability to merge branches into master as well as the ability to push changes on a master to its branches (git rebase)

      A---B---C feature                             A'--B'--C' feature
     /                   --rebase-->               /
D---E---F---G master                  D---E---F---G master

And btw, the duplicated community files needs to somehow stay attached to its original file to listen to changes and enable update when the source is updated

THIS. Or at least “versioning” in general. To my understanding, currently the versioning really is only 2 versions:

1. Current version
2. Any older versions

A common use case for Design Systems in larger organisations, is to support different versions of the same DS (libraries) for different teams and/or products.