We had this two times today already, so I wanted to file a report about it.
We created a branch in our library.
We did changes in this branch.
We successfully merged the branch back to our library. But the changes didn’t make it into the main file.
When we use the history function we can a) see, that a branch was merged and b) see that the changes didn’t make it to main. As soon as we jump into the branch that was merged, we can see the changes.
I am working on version 101.6. Happy to let you in the file if it helps.
Hi I’m having this exact issue across multiple files and projects. Same workflow and same working version. Would love some tips on how to prevent or reduce the occurrence of this bug. Thanks!
Same issue. This is of course a deal breaker that prevents us from continuing to work with branches. Good communication on this issue would be highly appreciated.
For anyone who wants to recover their work you can open the branch in archived branches and duplicate it as a new file. then manually copy the frames back to the main branch of the original file.
Sorry for the lack of public communication here - I’ve been DMing with some folks to try to get some examples to help us understand and debug this issue. I will continue to post updates here as I have them.
The merging process is super sloppy and broken still, some of my branches don’t apply Main’s changes, so when trying to merge that branch it will think I need to REVERT the changes in main that didn’t sync up
Figma 116.5.17 experiencing the same error.
The branch is “merged”, archieved and is not available to restore or edit; the main file haven’t been updated
Most of these were solved via DMs with RJ above, or on a case by case basis. Please reach out to the support team directly via this form for help: https://help.figma.com/hc/en-us/requests/new