Repository navigation
Build Method dependency graphs from GitHub Issues #72
Description
Idea
Teach Method to build a dependency graph from GitHub Issues instead of filesystem backlog links.
The old filesystem backlog had Depends on: fields and task-matrix/DAG generation. After the GitHub Issues migration, the natural replacement is an issue graph over explicit issue references and labels.
Possible shape
- Parse issue bodies for
Depends on: #123,Blocks: #456, and GitHub task-list relationships. - Emit
method graph --githubas Markdown, DOT, SVG, or JSON. - Compute frontier work: open issues with no unresolved blockers.
- Compute critical path by dependency depth.
- Detect dependency cycles across issues.
- Respect Method lanes and legends as graph metadata.
Why it matters
GitHub Issues are contributor-friendly, but dependency legibility can degrade fast. Method should recover the old task-matrix/DAG advantages without resurrecting repo-local backlog files.
Acceptance sketch
- A repo with no live
docs/method/backlog/**can still produce a Method dependency graph. - The graph uses GitHub Issues as nodes and preserves lane/legend/type labels.
- Cycles fail a doctor/check command.
- Frontier output is deterministic enough for CI and PR comments.
Activity
coderabbitai commentedon Jun 1, 2026
🔗 Related PRs
#64 - Make GitHub Issues the Method work tracker [closed]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!