Skip to main content

Maybe on confused on how the feature works. If the team is using for ideation and keeping the master branch clean for devs and clients. When it comes time to push elements from a branch to the master file, currently it pushes the entire branch. This is pointless. We don’t want all the ideation, all the options, all the throw away work, just the version that we moved forward with.


Currently we need to make a new branch we call “to be merged” and we need to copy just the artboards that are approved into the new branch then merge from there. This feels like to many steps and is complicated on a team of 4 designers. Shouldn’t there be an option to select just the artboards, components, styles, etc that we want to bring forward and leave all the other work in the archived branch incase we need to go back and grab something from it in the future?

Pushing everything makes the feature feel useless because you’re either deleting all your ideation or creating “merge” branches to make sure you don’t lose your work.

May I know if this is in the pipeline? This feature is pretty much useless without the ability to select what to merge.

Merging is a chaotic in a file with a lot of pages and with more than one people working on. We should be able to merge only one page or component, with a option to lock or not lock a page or component when a branch is created.

No one from Figma seems to be on this thread but just wanted to add my +1 to this

Would love to be able selectively merge, just like we can selectively publish components

Well, well, well
Just upgrade to Organization for branches… what a deceptive move.
How can I not choose what to merge ???
————————————————————
I will keep branches without merging* as archives, and copy-paste what I keep to the truth file.

* like this, I hope that the saturation of servers with heavy weighted file will make Figma to hear us about this non-ecological method

 

+1 I’ve been trying out branches for my latest project. Coming from a development background, it does not work as expected. I thought I want just using it wrong, but it seems like from reading threads here that there just isn’t really deep functionality. It’s very hard to pick and choose specific elements to come forward into my branches, while not merging things that will ruin my branch for my specific situation. I currently don’t trust the results, and the lack of specificity makes this feature more or less unusable. 

I don’t know what the excuse is for ignoring the community on this one. This is almost bare minimum functionality you would expect from a branching system in design software. 

Reply


Terms & ConditionsCookie settings