Feature Request: Branching: Ability to revert/discard changes in the "Branch Review" Overlay

is there any status or update on this? it feels crazy that I can’t easily revert changes due to unintended clicks. I find myself constantly mashing undo to make sure I don’t cascade updates in an unintended manner.

This issue becomes particularly problematic in large companies. Transferring your modifications to another branch isn’t a viable solution because it breaks the connections between components.

What’s even more frustrating is that at times, it indicates that a change has occurred, but when you review it in the comparison view, there is no clear explanation for the modification. So, is there really a change at all?

+1 very much needed

I went searching for this thread to find out I’d already commented on it 11 months ago! Guess this is an annual struggle for me.

One of my variants in an icon button with auto layout on it says the horizontal constraint has changed from scale to center. It’s just one variant, not all the variants, and there isn’t a single layer that I even have access to the constraints panel with, so I really have no idea how to deal with this. I can’t undo it, I can’t modify it to get rid of it, and I have no idea how it happened since I was editing a completely unrelated component. I would love to be able to discard this change since I’m fairly certain it’s a bug, but right now, to keep working, my only choice is to accept it, publish to my team, and hope it doesn’t break anything. Discarding would be ideal in this situation.

+1 much needed. I think it’s crazy we cannot include/exclude yet what we want to merge request during the review

Branching without usable conflict resolution makes life much harder than it should be.

Has there been any communication revolving around this?
With the advancements towards MCPs I would expect Figma to go full steam into actually useful Design System features and experience.
→ Being able to select/discard changes and actually make conflict resolution but also branching/merging useful and performant.

For any change, we should have the ability to disgard it. I like the “candling” feature but its more of a printed books feature and isn’t enough for software - you’ll need something like a conjoined “Diff/Candling” experience.