Repository navigation
docs: record that a closing keyword binds to one issue - #371
Merged
Merged
Conversation
raymondk
approved these changes
Sep 14, 2026
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
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
#370 was written to close ten issues with a single
Closes #360, #361, #362, ...line. It closed #360 only; the other nine stayed open and had to be closed by hand. GitHub binds a closing keyword to one reference and treats the rest of a comma-separated list as plain mentions.Adds two sentences to the Submitting section of
AGENTS.md: repeat the keyword per number, and check afterwards that they all closed.Why this is worth a rule
The upstream watcher will keep producing batches of issues that one sync PR closes, so this exact shape recurs by design. The failure is silent: the PR merges, the list looks right, and the issues quietly stay open.