fix(stack): record ChatMarkdown.tsx conflict resolution for auto-rebase - #144
Merged
Merged
Conversation
Stack sync fails replaying the root fork/changes commit onto fork/candidates when ChatMarkdown diverges (markdown image / browser link work vs candidates). Prefer the replayed fork/changes side via a durable commit:\"*\" policy so the next sync auto-resolves.
patroza
enabled auto-merge (squash)
July 28, 2026 12:11
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rebase-pr-stack.ts sync --push) fails onfork/changeswhile replaying1f8a2c58ontofork/candidateswith a conflict inapps/web/src/components/ChatMarkdown.tsx.commit: \"*\"+ exact-SHAtheirspolicies so the next stack rewrite auto-takes the fork/changes side (markdown images / browser link work).Test plan
vp check