584608a14e
Cherry-picked website/, scripts/generate-llms-full.sh, and deploy-docs.yml from joyshmitz's PR. Fixed workflow to trigger on main branch instead of docs/docusaurus-site. Features: - Docusaurus documentation site with llms.txt support - Environment-variable driven config (defaults to steveyegge org) - Automated llms-full.txt generation from docs - GitHub Pages deployment workflow Co-authored-by: joyshmitz <joyshmitz@users.noreply.github.com> 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> Executed-By: beads/crew/dave Rig: beads Role: crew
1.2 KiB
1.2 KiB
sidebar_position, title, description
| sidebar_position | title | description |
|---|---|---|
| 4 | Circular Dependencies | Detect and break dependency cycles |
Circular Dependencies Recovery
This runbook helps you detect and break circular dependency cycles in your issues.
Symptoms
- "circular dependency detected" errors
bd blockedshows unexpected results- Issues that should be ready appear blocked
Diagnosis
# Check for blocked issues
bd blocked
# View dependencies for a specific issue
bd show <issue-id>
# List all dependencies
bd dep tree
Solution
Step 1: Identify the cycle
bd blocked --verbose
Step 2: Map the dependency chain
bd show <issue-a>
bd show <issue-b>
# Follow the chain until you return to <issue-a>
Step 3: Determine which dependency to remove Consider: Which dependency is least critical to the workflow?
Step 4: Remove the problematic dependency
bd dep remove <dependent-issue> <blocking-issue>
Step 5: Verify the cycle is broken
bd blocked
bd ready
Prevention
- Think "X needs Y" not "X before Y" when adding dependencies
- Use
bd blockedafter adding dependencies to check for cycles - Keep dependency chains shallow when possible