Repository navigation
error about issue not being able to be closed yet it was #122
Description
thirdshift: warning: could not close issue #114, so if it is still open, close it by hand: gh issue close 114 --repo JacobStephens2/thirdshift --comment 'Closed by #121, merged into main by a thirdshift Merge run.'
thirdshift: cleaning up the worktree and local branch issue-114
thirdshift: PR #121 is merged
#121
jacob@tracewake:/repos/thirdshift$ gh issue close 114 --repo JacobStephens2/thirdshift --comment 'Closed by #121, merged into main by a thirdshift Merge run.'/repos/thirdshift$
! Issue #114 (--email sends a Run notification whenever a Run ends) is already closed
jacob@tracewake:
Activity
JacobStephens2 commentedon Sep 30, 2026
Already fixed. The warning was wrong: GitHub closed #114 itself a moment after #121 merged, because #121's body says
Closes #114.Before closing the issue, thirdshift v0.3.0 asked
gh pr view --json closingIssuesReferenceswhether the merge would close it.gh2.45 doesn't support that field, so the call failed and thirdshift reported the failure as "could not close issue #114".#181 reported the same failure, and #186 (commit f2ab46a) fixed it. After a merge, thirdshift now checks only the issue's
stateand closes the issue if it is still open (close_unless_closedinsrc/run.rs). The fix shipped in v0.4.0.