You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fail a PR whose close keywords sit in prose that says the issue stays open #672
Close keywords in prose have shut eight issues by accident
GitHub reads close/closes/fix/fixed/resolve followed by #N anywhere in a PR body or commit message, including inside a sentence that says the opposite, after a colon, or across a line break. This repo uses Refs #N on purpose for work that closes on a physical act or a deploy. Its prose keeps tripping the matcher anyway:
#182, #251 and #571 sat closed for days to weeks with the work undone and no tracker. They were found only by a full pass on 2026-09-26.
Checking by hand after opening a PR (closingIssuesReferences) is the current mitigation, and it has not been enough.
What to build
A PR check that reads closingIssuesReferences over GraphQL and fails when any linked issue is also named with Refs in the same body, or appears in a sentence containing not, nothing or stays open. At minimum it should write the list of issues the merge will close into the job summary, so it is visible before merge. A commit-message scan for the same patterns catches squash bodies.
Activity
docs(roadmap): list #671 and #672, filed in the 2026-09-26 pass (#673)
fix(ci): close-keyword check review fixes