Skip to content

Resolve merge conflict markers in 7 files - #290

Open
seriouscoderone wants to merge 4 commits into
WebOfTrust:mainfrom
seriouscoderone:main
Open

Resolve merge conflict markers in 7 files#290
seriouscoderone wants to merge 4 commits into
WebOfTrust:mainfrom
seriouscoderone:main

Conversation

@seriouscoderone

Copy link
Copy Markdown
Collaborator

Summary

  • Resolved unresolved merge conflict markers (<<<<<<<, =======, >>>>>>>) across 7 files that were left over from a previous 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 4 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>
Resolve merge conflict markers in 7 files
…reamer.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@seriouscoderone

Copy link
Copy Markdown
Collaborator Author

Still mergeable and clean. Worth prioritising independently of the LLM-docs work: main currently has unresolved merge conflict markers committed in 5 published files —

  • docs/04_glossary/self-authenticating.md
  • docs/04_glossary/streamer.md
  • docs/08_annotated-copies/WebOfTrust-ietf-acdc-main-draft-ssmith-acdc.md
  • docs/08_annotated-copies/WebOfTrust-ietf-cesr-proof-main-draft-pfeairheller-cesr-proof.md
  • docs/08_annotated-copies/WebOfTrust-ietf-ipex-main-draft-ssmith-ipex.md

Verified today with git grep -lE '^<<<<<<< |^>>>>>>> ' against main. These render as literal <<<<<<< markers on the published site.

Happy to narrow this PR to only the conflict-marker fix if that would ease review.

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