Merge conflict detected
Original PR title: feat(app): add copy rich text option for message content
Detected: 2026-04-28T06:29:09.619Z
Watson Guidance
- Conflicting file(s) / conflict type: No conflicting files are captured in the provided evidence (
Conflicting files: none captured), so no exact file path or git conflict type can be identified from the evidence.
- Base branch version: The provided evidence does not include any base-branch excerpts for a conflicted file, so it is insufficient to say what the base branch is doing in any specific conflicting file.
- Head branch version: The head branch changes shown are limited to the PR file list and description: it adds rich-text copy support, clipboard HTML/plain-text payload handling, settings for copy mode, and related UI/tests across the listed
packages/app/... and packages/ui/... files, but no conflicted-file excerpt is provided.
- Safest resolution / verify after push: First obtain the actual merge-conflict file list and conflict markers or a base-vs-head diff for the conflicted file(s); without that, the conflict trigger cannot be distinguished from the PR’s broader feature changes. After resolving and pushing, verify the conflicted file(s) compile, the copy-mode settings UI still works, rich-text/plain-text copy behavior still works, and the relevant tests/validation pass.
Resolve locally
git fetch origin
git checkout feature-branch
git merge origin/main
# resolve conflicts
git push
Merge conflict detected
Original PR title: feat(app): add copy rich text option for message content
Detected: 2026-04-28T06:29:09.619Z
Watson Guidance
Conflicting files: none captured), so no exact file path or git conflict type can be identified from the evidence.packages/app/...andpackages/ui/...files, but no conflicted-file excerpt is provided.Resolve locally
git fetch origin git checkout feature-branch git merge origin/main # resolve conflicts git push