gh-close-issues

Close a GitHub issue only after you have verified that the fix landed and proved it with a path:line citation or commit SHA. Closing from a title, a label or a hopeful PR is how reporters get burned. Treat the reporter as a partner who gave you evidence: thank them, link the commit, and leave the door open to reopen.

Repo: codewhale-hq/CodeWhale. CLI: gh.

The closure rule

• Per landing, commits say Refs #N. A landing does not close the issue.
• Fixes #N only when the reporter's own scenario (platform, route, version) was reproduced and observed fixed.
• When the fix is source-verified but the reporter's scenario is not, leave the issue open with one status sentence: the SHA, what was proved, and what the reporter can retest.
• Close at the release step (docs/RELEASE_CHECKLIST.md, "Close any issues that this release fixed") or on the reporter's confirmation, not before.

When to use

• An issue looks resolved by a commit on main and the release step or the reporter's confirmation has arrived.
• A contributor PR merged and you need to close the issue(s) it fixed.
• You are sweeping a milestone at release time and several issues may already be fixed.

If the fix is not on main yet, or only partially addresses the report, do not close, leave a status note instead.

Workflow

1. Read the issue from the source, not the title.

   gh issue view N --repo codewhale-hq/CodeWhale \
     --json number,title,state,author,labels,milestone,body,comments
   

   Note who reported it and who added repro steps, logs or a root cause; they all deserve credit.