Create GitHub Issue Dependencies
Use issue Relationships to mark blocking and blocked-by work with the correct direction. A dependency explains sequencing; it does not automatically validate that the prerequisite is suitable or complete.
Step-by-step guide
Check access and scope
Creating dependencies requires at least triage permission in the repository. Both issue owners should agree on the actual unblock condition.
Identify the prerequisite
Open the dependent issue and identify its prerequisite.
Mark the blocked relationship
In Relationships choose Mark as blocked by. The issue sidebar Relationships menu offers Mark as blocked by and Mark as blocking; choose the option from the perspective of the issue currently open.
- Worked example: The invitation UI can depend on a stable token-validation contract. A related terminology discussion should not block implementation unless its outcome truly prevents the next step.
Select the blocking issue
Select the appropriate issue and review the resulting link.
Explain the handoff
Explain the expected artifact or condition in a comment.
Inspect both records
Inspect both issue records and remove obsolete relationships.
Verify the result
The dependent issue displays the intended blocked relationship and owners can explain how to clear it.
Common mistakes
Check the handoff edge case
A dependency without a concrete unblock condition can outlive its purpose. State the artifact or decision the dependent work needs.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.