docs: GH-253 state the PR linking mechanism correctly - #262
Open
joaodinissf wants to merge 1 commit into
Open
Conversation
joaodinissf
enabled auto-merge (rebase)
July 29, 2026 17:37
joaodinissf
disabled auto-merge
July 30, 2026 20:17
GH-<issue> is a built-in GitHub reference form and resolves in commit messages without any autolink configuration; the /autolinks endpoint lists only custom autolinks. What does not resolve is any reference in a title. Since the repo is rebase-merge only, the commit message is the sole durable carrier of a reference — so the title prefix matters precisely because it is mirrored into the commit subject. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
joaodinissf
force-pushed
the
docs/linking-mechanism-fix
branch
from
August 1, 2026 16:39
d1d9bad to
91d4038
Compare
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.
#254 merged at a stale head, so the correction it carried never reached
main.CLAUDE.mdcurrently claims GitHub does not resolveGH-<issue>because no autolink is configured. That is wrong twice over.GH-<issue>is one of GitHub's built-in reference forms and resolves in commit messages with no autolink configuration — the/autolinksendpoint lists only custom autolinks. Commit31bc9c2ecarries onlyGH-168andGH-248, no bare#N, and both issues receivedreferencedevents from it.What genuinely does not resolve is any reference in a title,
GH-or bare#Nalike. That is what made #247 invisible from #168.And because this repo is rebase-merge only, the PR body never enters history — so the commit subject is the one reference that survives the merge, which is precisely why the title prefix is worth keeping.
Relates to #253
This pull request was published with assistance from Claude.