fix(kanban): check GitHub PR state before applying active_pr respawn guard - #29492
Closed
nasymonk wants to merge 1 commit into
Closed
fix(kanban): check GitHub PR state before applying active_pr respawn guard#29492nasymonk wants to merge 1 commit into
nasymonk wants to merge 1 commit into
Conversation
…guard The respawn guard previously treated any GitHub PR URL in a recent task comment as evidence of an active PR, blocking the task from being re-spawned for 24 hours — even if the PR was already closed/merged. Now checks the GitHub API to verify PR state. Closed/merged PRs skip the guard so operators aren't stuck waiting 24h after closing a stale PR. On API errors (rate-limit, network), falls back to the safe assume
alt-glitch
added
type/bug
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
active_prrespawn guard previously treated any GitHub PR URL in a recent task comment as evidence of an active PR, blocking the task from being re-spawned for 24 hours — even if the PR was already closed/merged.This left operators stuck with
respawn_guarded {"reason": "active_pr"}on a loop, with no supported recovery path except waiting 24h or manually editing SQLite.Fix
Testing
Verified against the exact scenario from #29458:
_is_github_pr_closed()returns True → guard skipped ✅Fixes #29458