Skip to content

Resolve merge conflict markers in 7 files - #1

Merged
seriouscoderone merged 2 commits into
mainfrom
fix-merge-conflicts
Feb 16, 2026
Merged

Resolve merge conflict markers in 7 files#1
seriouscoderone merged 2 commits into
mainfrom
fix-merge-conflicts

Conversation

@seriouscoderone

Copy link
Copy Markdown
Owner

Summary

  • Resolved unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>) across 7 files that were left over from an upstream merge
  • Affected files include glossary entries, specification docs, overview content, and config files

Test plan

  • Verify no remaining conflict markers in the codebase
  • Confirm site builds correctly with resolved files

🤖 Generated with Claude Code

seriouscoderone and others added 2 commits February 16, 2026 01:00
These files contained <<<<<<< HEAD / ======= / >>>>>>> upstream/main
conflict markers that were committed without being resolved. Keeps the
upstream/main side in all cases:
- 3 annotated-copies files (different auto-generated accordion IDs)
- 2 glossary files (self-authenticating.md, streamer.md)
- overview-and-context.mdx (auto-generated table data)
- overview.json (auto-generated JSON data)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@seriouscoderone
seriouscoderone merged commit 1fba8ae into main Feb 16, 2026
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