Fix committed merge-conflict markers in docs; add marker scan to release check#33
Merged
Merged
Conversation
…ase check The #32 rebase left unresolved conflict markers in CHANGELOG.md, README.md, and docs/deployment_runbook.md that were committed and merged to main. Resolved each as the union of both sides, dropping each branch's stale "remains a design gate" cross-reference now that both #24 and #2 have shipped. vmga_release_check.py now scans all repo text files for conflict markers and fails on any hit, so this class of error cannot pass the release gate again. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The #32 rebase left unresolved conflict markers committed in CHANGELOG.md, README.md, and docs/deployment_runbook.md (maintainer error: blanket `git add -A` after resolving only the code conflict; CI and the release check had no marker detection). This PR:
Verification: release check PASS, `python -m pytest -q` → 124 passed, `git diff --check` clean.
🤖 Generated with Claude Code