feat: add idempotent tracker-aware setup-dev-backlog (#277)#301
Conversation
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Relay ReviewVerdict: LGTM |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26482d6b8d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| const nextRaw = configExists | ||
| ? mutateTrackerText(raw, configState, selection) | ||
| : freshConfig(projectName, selection); |
There was a problem hiding this comment.
Guard missing configs before selecting local tracker
When backlog/ already contains task files but config.yml is missing, this branch writes a fresh config using the requested selection, so --tracker local can silently flip a legacy checkout from the runtime default GitHub authority (lib.js lines 32-34) to local. Existing GitHub mirrors use id: BACK-N (sync-pull.js lines 195-197), and the local adapter accepts that same id/ref shape (local-tracker.js lines 322-340), so those issue mirrors are immediately treated as local tasks instead of failing closed like the tracker-less-config path does. Please guard missing-config-but-nonempty backlog before allowing a direct local switch.
Useful? React with 👍 / 👎.
Summary
setup-dev-backlog.jsentrypoint with explicitgithubandlocaltracker selectionValidation
node --test skills/dev-backlog/scripts/setup-dev-backlog.integration.test.js(17/17)node --test skills/*/scripts/*.test.js(639 pass, 1 existing opt-in skip)bash skills/dev-backlog/scripts/smoke-test.sh(155/155)git diff --check26482d6Closes #277