fix(dashboard): clear "needs action" on recent advances after manual sync
The Git Manager's recent integration-advances list derived `needsAction` purely from the original `merge:auto-sync` audit-event outcome, so it kept showing "(N need action)" after the operator clicked "Sync working tree" or fixed up the worktree by hand. `collectRecentMergeAdvances` now also checks whether each advance's `toSha` is reachable from HEAD — if it is, the worktree already contains that advance and `needsAction` is false regardless of what the audit trail recorded. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
9
.changeset/fix-recent-merge-advances-needsaction.md
Normal file
9
.changeset/fix-recent-merge-advances-needsaction.md
Normal file
@@ -0,0 +1,9 @@
|
||||
---
|
||||
"@fusion/dashboard": patch
|
||||
---
|
||||
|
||||
fix(dashboard): clear `needs action` on recent integration-branch advances after manual sync
|
||||
|
||||
The Git Manager's "Recent integration-branch advances" list derived `needsAction` purely from the original `merge:auto-sync` audit-event outcome. When the operator clicked "Sync working tree" — or fixed up the worktree by hand — the worktree caught up to the integration tip, but the list kept showing "(N need action)" because the historical audit events still recorded the original failure/disabled state.
|
||||
|
||||
`collectRecentMergeAdvances` now also checks whether each advance's `toSha` is reachable from the current HEAD. If it is, the worktree already contains that advance and `needsAction` is false regardless of what the audit trail recorded.
|
||||
Reference in New Issue
Block a user