Summary
After squash merging via parsec merge, the associated GitHub issue is not auto-closed because the Closes #N from the commit body is lost during squash. Users must manually close issues.
Proposed Behavior
parsec merge should auto-close the associated issue after a successful merge, using the GitHub API:
PATCH /repos/{owner}/{repo}/issues/{number}
{"state": "closed", "state_reason": "completed"}
This should be opt-out via --no-close-issue flag or config option.
Context
Every merged PR in our workflow requires a separate gh issue close command. This adds friction to the workflow.
Summary
After squash merging via
parsec merge, the associated GitHub issue is not auto-closed because theCloses #Nfrom the commit body is lost during squash. Users must manually close issues.Proposed Behavior
parsec mergeshould auto-close the associated issue after a successful merge, using the GitHub API:This should be opt-out via
--no-close-issueflag or config option.Context
Every merged PR in our workflow requires a separate
gh issue closecommand. This adds friction to the workflow.