You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(prd): keep a PRD it cannot read so its number is not reissued
listPrds discarded any PRD whose readFileSync threw. That contradicts the
rest of the same loop: a PRD whose front matter will not parse is kept on
the slug and "?" fallbacks, which two existing tests assert.
The consequence is not a missing row. nextId takes its max from this list,
so dropping a PRD hands its number straight back out and two PRDs end up
numbered the same, in a scheme where the number is the identity. A
committed symlink whose target is not checked out is enough to trigger it:
readFileSync throws ENOENT, so it arrives from a plain clone.
Keep the entry on the same fallbacks the unparseable case already uses.
The id stays reserved and the index row keeps its link.
0 commit comments