Skip to content

chore: use merge conflict bool instead of message parsing#9581

Merged
AdityaHegde merged 2 commits into
mainfrom
chore/use-merge-confict-message
Jun 18, 2026
Merged

chore: use merge conflict bool instead of message parsing#9581
AdityaHegde merged 2 commits into
mainfrom
chore/use-merge-confict-message

Conversation

@AdityaHegde

Copy link
Copy Markdown
Collaborator

Follow up to #9580 . Moves frontend to use the conflict bool instead of error message parsing.

Checklist:

  • Covered by tests
  • Ran it and it works as intended
  • Reviewed the diff before requesting a review
  • Checked for unhandled edge cases
  • Linked the issues it closes
  • Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
  • Intend to cherry-pick into the release branch
  • I'm proud of this work!

@AdityaHegde AdityaHegde requested a review from k-anshul June 18, 2026 06:26
@AdityaHegde AdityaHegde merged commit 3c4d307 into main Jun 18, 2026
13 checks passed
@AdityaHegde AdityaHegde deleted the chore/use-merge-confict-message branch June 18, 2026 07:24
AdityaHegde added a commit that referenced this pull request Jun 18, 2026
* chore: use merge conflict bool instead of message parsing

* Add conflict resolution dialogs for self-managed git paths
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants