I want to create a branch of a library.
I then want to use components from the library branch, in another file.
Once the project is live, I would then merge the library branch back into the main file.
This is a way to manage work in progress changes to a component that are used in a project, and then a way to make that change live, once the project goes live.
8 Likes
The answer is no. This is a shame as is a common workflow pattern.
3 Likes
I would really love to have this capability as well. I’m trying to build a DRY environment because the previous approach was just things everywhere and I find myself never knowing where to find the latest changes to any part of the system. Some little update is always buried away inside X and Y projects whose Figma elements don’t overlap in any way. In fact, with how branches work today, you can’t have X and Y change shared elements in two different branches at the same time… I mean, you could have two branches, but you couldn’t actually USE the changes… so you’d be encouraged to just make local changes.
Branches are still great but they could be improved.
1 Like