Git Like versioning

+1 On Git Like Versioning!

+1, really need that kind of feature for large design team

For me this is one of the biggest problems in Figma and the new Abstract plugin is oriented towards communication, not versioning. Hopefully this will get some traction.

@Diego That’s a good reason to vote 🙂

1. Describe the problem your experiencing and how your idea helps solve this

You really cant track what kind of change was made to the library file, change can be registered even from X Y position change, etc.

I would love to see some change list, as git has before and after. Specific information about what I’m about to update to the library. Selecting what changes to publish would be a good add-on also. I may have some drafts that I want to publish later time.

*3. Ask questions to bring the community into the conversation *
(e.g. Does anyone else experience this? Is anyone using a plugin or workaround to help solve this?, etc.

Hello and welcome @Erno_Tuovinen 🙂 You’re definitely not the only one experiencing this. Please vote 🔝

It would be amazing to have this for community UI kits too! Where I can fork a UI Kit and then when the creator updates their file, I can merge those updates into my copy.

We don’t need “git like” functionality in figma - git already does that. What we need is the ability to use git itself within figma and to integrate and connect with tools like gitlhub, gitlab, and bitbucket. Figma could use git in such a way - at a fundamental level - that you are able to use actual git from within figma (pushing, pulling, cloning, branching, merging… all of it) just like an IDE integrates with git and allows you to work with it from within the IDE. Figma doesn’t need to replace git. Git does a wonderful job of version control already; and, frankly, having figma do something like it would just add more tools that do the same thing to the workflow. In addition, your project would become split between the two tools and you would be separating parts of the team from one another as a result. By integrating git into figma you could keep all stages \ phases of your project in one place → git - and work with one tool for all of it. By keeping figma projects in a git repository you could either make a dedicated branch in git for “design” or a repository of it’s own. Either way you would also then have all the stuff that comes with the repository (issues, boards, kanban, scrum, wiki, all of it). Let git do what it does best and figma do what it does best and combine the two. That scenario increases what both tools are able to do exponentially!

PS: Then people could start making plugins for your IDE that would allow you to work with figma (if even in a limited sense) in your IDE - integrating git with figma would open up that possibility.

Examples:

• It would open up the possibility for a plugin to bring the properties and css stuff from a figma project directly into your IDE using a plugin via the figma in your git repository.

Here’s what a workflow with figma / git integration might look like…

• You create a repository for your entire project in github, gitlab, or bitbucket for your entire team (not just the designers but the devs and everyone else too).
• You create a branch in that repository either directly from within figma or through your IDE, the command line, or your cloud or self hosted management application of choice (github, gitlab, or bitbucket in this example) and then pull the branch into figma - either way).
• You work in figma on that branch being able to use full git functionality right in figma (or do manipulations on the branch outside of it in your IDE or management application of choice) and have that reflected.
• You push changes to your branch directly to upstream the same way you would from your IDE.
• You pull changes down from upstream to sync your branch with the rest of your team (figma still has its full team functionality which is needed - there is no cross over).
• When you finish a project in figma you can archive it (leave it upstream and take it out of active status - out of availability) in figma.
• If you need to work on the design aspect of that project again in the future you unarchive it or pull it back into figma (thus keeping your active projects in figma limited to just what you need).
• All the while your entire team is able to connect all the other functionality of your repository management system with the design part of the project allowing other non-design members of your team to interact with the design (board / project management features of github, gitlab, bitbucket for the pm members of the team, wiki for documentation, issues for review and feedback, etc)
• Then, when the design is finalized, the properties of the project get pulled into your IDE through a plugin from the figma content in the repository - right where it is needed so development can access it right in the IDE.

All because of integration with an existing, robust system that has robust features in it’s own lane.

Something like that ^

YES to Git versioning.

I’ve been working with developers over the years and Git versioning is the best system I’ve used so far, would be great to have in a full-cycle product design workflow. We really need this same versioning system for design process as we encounter so many issues with devs on designs, things get lost in translation, wrong things developed, or we spent huge amounts of time to make changelog and documentation for changes in pages…

We should collaborate and iterate seamlessly with our teams, just we do while we write code and develop the designs.

Currently in Figma, there is only version history, that has no value in product design cycle for teams. I’ve only used to restore couple of components.

Hope Figma team knows how important this is, and how much we suffer because of this.

Yes! https://help.figma.com/hc/en-us/articles/360063144053

It’s a bit disappointing that it’ll only be available on the Organization Plan… @figma Is it correct? What about Professional Plan?