Issue with Ready for Dev Tab Showing Incorrect Changes After Branch Merge

Hi Figma Community,

I'm encountering an issue with the "Ready for Dev" tab in Dev Mode after merging a branch, and I’d like to share the problem and see if there’s a solution or workaround to achieve the desired workflow.

The Problem

After merging a branch into the main file, the "Ready for Dev" tab correctly marks the affected section as Edited. However, when I click "Compare Changes" to review the updates, it displays incorrect comparisons:

• The "old" version shows the section as deleted (from before the merge).

• The "new" version shows the section as added, but it’s not the latest merged version—it’s the version of the section before the merge.

This creates confusion for developers because the comparison doesn’t reflect the actual changes made in the merged branch. As a result, they cannot see what was edited in the merged version directly from the "Ready for Dev" tab.

Current Workaround

To resolve this, I have to:

1. Mark the Edited section as Done in the "Ready for Dev" tab.

2. Manually mark the newly merged section as Ready for Dev again (I cannot manually set it to "Changed" status myself).

3. Instruct developers to navigate to the section directly in the document (not via the "Ready for Dev" tab, as it’s no longer marked as Edited) and use the "Compare Changes" option there to view the actual changes.

This process is inefficient because it requires developers to leave the "Ready for Dev" tab and manually locate the section in the document, defeating the purpose of having a centralized overview of changes.

Desired Workflow

I’d like the "Ready for Dev" tab to function as a single source of truth for developers. Specifically:

• After merging a branch, the affected sections should appear as Edited in the "Ready for Dev" tab.

• Clicking "Compare Changes" should show the correct comparison between the pre-merge main file and the newly merged version, so developers can clearly see what was changed without navigating elsewhere.

Questions

• Is there a way to ensure the "Ready for Dev" tab displays the correct merged changes in the "Compare Changes" view?

• Are there settings or steps I might be missing to make the "Ready for Dev" tab reflect the latest merged version accurately?

• Has anyone else experienced this issue, and if so, how did you address it?

Any insights, workarounds, or suggestions would be greatly appreciated! Ideally, I want developers to rely solely on the "Ready for Dev" tab to track and review changes without needing to dig through the document manually.

Thanks in advance for your help!