feat(pipeline): ADR gate opens a draft PR; PR gate marks it ready#689
Conversation
Rework the feature-pipeline-preview flow so the maintainer reviews on GitHub: - Phase 3 (ADR draft) now commits the ADR, pushes the branch, and opens a DRAFT PR — the maintainer reviews the ADR there instead of only on disk. pr_url/pr_number are recorded at this point. - Phase 16 (renamed "Create PR" -> "Finalize PR") no longer creates a PR; it commits/pushes the implementation, sets the final title/body via `gh pr edit`, and converts the existing draft PR to ready with `gh pr ready`. Refuses if no phase-3 draft PR exists. Updates the orchestrator SKILL.md (phase 3/16 descriptions + PAUSE-gate note), the phase-allowed-paths reference, and the PHASES[16] name in pipeline.py. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 12 minutes and 34 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ 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 |
2 participants
What & why
Reworks the
feature-pipeline-previewskill so the two maintainer gates produce and finalize a single PR, reviewable on GitHub from the ADR stage onward:pr_url/pr_numberare recorded here.gh pr edit), and flips the draft to ready for review (gh pr ready). It refuses if no phase-3 draft PR exists, so it can never open a second PR.Changes
03-adr-draft/SKILL.md— adds the commit + push +gh pr create --draftsteps; newbranch_name/sluginputs; updated Output/Assumptions/Refusals.16-create-pr/SKILL.md+16-create-pr/02-submit/SKILL.md— reframed from "create" to "finalize":gh pr edit+gh pr readyagainst the phase-3 PR instead ofgh pr create.SKILL.md(orchestrator) — phase 3/16 descriptions + the PAUSE-gate note.references/phase-allowed-paths.md— phase 3/16 rows.scripts/pipeline.py—PHASES[16]nameCreate PR→Finalize PR(no logic change;cmd_setalready acceptspr_url/pr_number).Notes
pipeline.pybehavior change — it already storespr_url/pr_numberviaset; only the phase name string changed (py_compileclean).ghand a repo that supports draft PRs (NeoHaskell is public).🤖 Generated with Claude Code