roadmap --auto-chain clears a chain head's existing on-disk depends_on
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #414 by @Kuldeep2822k — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
The bug is in src/cli/roadmap.ts around lines 154-162, where the chain head's depends_on is set to [], and line 273, where resolveTopicUpdates treats an explicit [] as a clear. Compare that branch with the cycle-skip branch, which leaves depends_on unassigned, and with the non-auto-chain path that preserves on-disk dependencies. Done means auto-chain keeps a head note's existing depends_on, and a test covers a head note with pre-existing dependencies run through roadmap --auto-chain.
Written by the indexing model from the issue text.
Description
Location: src/cli/roadmap.ts:154-162,273
The head topic (rank 0, no roadmap depends_on) is set to [], and resolveTopicUpdates treats explicit [] as 'clear', erasing the head note's pre-existing on-disk dependencies. Without --auto-chain the same entry preserves them. Running auto-chain therefore silently drops dependencies a learner previously authored on the head note.
Fix: Leave the head's depends_on unassigned (as the cycle-skip branch does) so existing deps are preserved.
From the 2026-10-10 codebase audit sweep (CODEBASE_AUDIT.md).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 23h 23m
- Merged PRs (30d)
- 163
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kuldeep2822k/cli
-
core priority: medium tests
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Kuldeep2822k/cli#484 ·
Maintainers usually reply within 1 day
-
bug core priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Kuldeep2822k/cli#343 · 1 comment ·
Maintainers usually reply within 1 day
-
bug core priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Kuldeep2822k/cli#342 · 1 comment ·
Maintainers usually reply within 1 day
-
bug core tests
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Kuldeep2822k/cli#514 ·
Maintainers usually reply within 1 day
-
bug tests
Difficulty 5/5 Over a week Newbie friendliness 25/100
Kuldeep2822k/cli#504 ·
Maintainers usually reply within 1 day
All issues in Kuldeep2822k/cli
Similar issues
-
bug P3 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
StellarState/SS-backend#712 ·
Maintainers usually reply within 1 day
-
area: backend bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
snapotter-hq/SnapOtter#3473 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
gitroomhq/postiz-app#2304 ·
Maintainers usually reply within 1 day
-
harlan-agent-ready-to-implement routine:ci-review
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
harlan-zw/unlighthouse#454 · 2 comments ·
Maintainers usually reply within 1 day