Managing GitHub Issue Dependencies

Use GraphQL mutations to create blocking relationships between issues. Convert issue numbers to node IDs, then apply the addBlockedBy mutation to mark one issue as blocked by another, enforcing ordered work and dependencies across your repository.

Yes. Query blocking and blocked-by relationships using GraphQL to retrieve current dependency relationships between issues, letting you see which issues are blocking others and which are waiting on completion.

The Skill includes circular-dependency prevention logic built into its blocking operations. It validates relationships before applying mutations, stopping you from creating scenarios where issues block each other in a loop.

Use the removeBlockedBy GraphQL mutation with safety checks to lift blocking relationships. The Skill verifies the operation and returns clear output, ensuring you don't accidentally break dependent workflows.

Yes. The Skill supports bulk operations to apply dependencies across multiple issues in a single workflow, making it efficient to establish complex dependency chains across your repository.

Yes. GitHub's GraphQL API requires node IDs rather than issue numbers for mutations. The Skill handles this conversion automatically, translating issue numbers into the node ID format required for blocking and unblocking operations.