Skip to content

feat(issues): blocked work links a new blocker issue - #268

Merged
tannerpolley merged 1 commit into
mainfrom
issue-267-paused-issues-that-are-blocked-become
Oct 31, 2026
Merged

tannerpolley merged 1 commit into
mainfrom
issue-267-paused-issues-that-are-blocked-become

Conversation

@tannerpolley

Copy link
Copy Markdown
Owner

Paused issues that were stuck on something outside their scope stayed Paused, with nothing recording the blocker.

  • propose_issue_change gains a blocked_by operation (add/remove) through the existing issue-change path: GitHub addBlockedBy/removeBlockedBy, Forgejo issue dependencies. Same approval policy, conflict checks and lost-response recovery as sub_issue.
  • Managed implementors and issue owners are told: when an outside blocker stops them, create an issue for it, link it with blocked_by, and end with a final result naming it. Not for owner questions or failing tests within scope.
  • The issue then shows Blocked; closing the blocker returns it to Paused.
  • Agent-context budget 72,456 → 72,539 bytes (measured). Free eval --context/--dry-run checks pass; paid evals not run.

Closes #267

Implemented by GPT-6.1 Sol (Codex) in T3 Code; reviewed by Claude Opus 5.5.

🤖 Generated with Claude Code

@tannerpolley
tannerpolley merged commit 8f5c7e6 into main Oct 31, 2026
@tannerpolley
tannerpolley deleted the issue-267-paused-issues-that-are-blocked-become branch October 31, 2026 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Paused issues that are blocked become Blocked, with a new issue for the blocker

1 participant