docs: standing authorization to self-merge future doc-sync PRs - #9
Merged
Conversation
…e branches; fix stale title count
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
2 participants
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.
Summary
Requested directly by the project owner today, in response to finding that this repo (and the other three in the same portfolio) had accumulated two near-duplicate "docs: sync" draft PRs each — the recurring documentation-sync task lands on a fresh randomly-named branch every run, so an unmerged PR from the previous run was never being reused or reconciled.
Change
Two small edits to
CLAUDE.md:tests.yml) is green, without waiting for a chat confirmation each time — and, before opening a new PR, to check for and consolidate with any other still-open "docs: sync" PR on the repo rather than leaving two open.Scope is deliberately narrow: documentation-only changes from this one recurring task, never the measurement-track/product code, gated on CI same as any other merge.
Today's cleanup (already done, for context)
PR #7 and #8 both existed as near-duplicate doc-sync PRs; #8 (carrying forward #7's unique release badge + "Ground truth, precisely" callout) is merged, #7 is closed with a note pointing to it.
Generated by Claude Code