Skip to content

docs: require Closes #N in PR bodies so issues auto-close on merge #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Rinse12 merged 1 commit into from
Sep 1, 2026
Merged

docs: require Closes #N in PR bodies so issues auto-close on merge #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,8 @@ When the user gives a prompt to implement a feature or bug fix in this repositor

1. **MUST** create a GitHub issue for the feature before starting work (`gh issue create`).
2. **MUST** keep the issue updated with the current plan and progress as work proceeds.
3. **MUST** ask the user whether to close the issue after the feature is fully implemented and verified — do not close it automatically or via `Closes #N` in commit messages.
3. **MUST** put `Closes #N` in the PR body so the issue auto-closes when the PR merges. Closing keywords go in the PR body only, never in commit messages.
4. **MUST** ask the user before closing an issue manually (`gh issue close`); auto-close via PR merge needs no ask.

Routine live operations are not repository feature work:

Expand Down