feat: enroll .github in the idea→initiative pipeline + document caller stubs#504
Conversation
…r stubs - Adopt the initiative-planner caller stub on petry-projects/.github itself (the S8 pilot): on `idea:approved` it dispatches the central BMAD planner with .github as target_repo, materializing an inert epic in this repo. - ci-standards.md §10 documents the three idea→initiative caller stubs, the thin-stub→dispatch-reusable→central-planner architecture, the two human gates, the hybrid project-board funnel (consumer repos → repo project; .github/ .github-private → org project #1), and the adoption runbook. Refs petry-projects/.github-private#817, #824, #825 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 51 minutes and 1 second. 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 refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughAdds a new GitHub Actions workflow ChangesInitiative Planner Caller Stub and CI Standard
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds documentation for the "Idea → Initiative pipeline" in standards/ci-standards.md, detailing its architecture, prerequisites, project-board funnel, and adoption steps for BMAD Method repositories. Feedback points out a broken anchor link to add-to-project.yml and a duplicated section number (10.), suggesting corrections for both.
Dev-Lead — review-changes (applied)Changes committed and pushed. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@standards/ci-standards.md`:
- Line 1009: The markdown fragment link for `add-to-project` contains an
incorrect anchor identifier `#add-to-projectyml` that does not match the actual
heading slug generated by the markdown renderer. Locate the correct heading for
the add-to-project section in the file and update the fragment link to use the
proper heading slug, or alternatively use a direct file link instead of a
fragment reference to ensure the markdown lint validation passes.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 4c95c3c6-9b3f-439e-8da9-90e4e0edc828
📒 Files selected for processing (2)
.github/workflows/initiative-planner.ymlstandards/ci-standards.md
petry-projects/.github hosts the initiative-planner reusable, so its own active stub must use a LOCAL `./` ref (like add-to-project.yml / pr-review-mention.yml), not the `@initiative-planner/stable` remote channel that consumer repos pin. Resolves the SonarCloud "use full commit SHA" security finding (a remote tag ref on the hosting repo) without SHA-pinning a first-party reusable (forbidden by ci-standards.md). The standards/ template keeps the @stable ref for consumers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
@donpetry-bot please review — code-owner approval needed to merge. CI green (SonarCloud now passes after the self-host local-ref fix). |
|
@don-petry I'm on it — starting a fresh review now. Results will appear in a few minutes. |
Superseded by automated re-review at
|
|
@donpetry-bot review please — code-owner approval still needed; CI is green (SonarCloud passing). |
|
@don-petry I'm on it — starting a fresh review now. Results will appear in a few minutes. |
donpetry-bot
left a comment
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: LOW
Reviewed commit: 3287e6746a8181d1925d0e6be79d32eb4929389a
Review mode: triage-approved (single reviewer)
Summary
Adds a clean initiative-planner thin caller stub (permissions: {}, correct first-party LOCAL ./ self-host ref — un-SHA-pinned per ci-standards.md, mirroring add-to-project.yml/pr-review-mention.yml; secrets: inherit; no untrusted-input interpolation; no secrets) plus a ci-standards.md section documenting the idea→initiative pipeline. Triage cleared this as low-risk and this confirmation review agrees: no security or GitHub Actions smell (the trusted-actor gate lives in the reusable by design), CI is fully green (SonarCloud/CodeQL/gitleaks/ShellCheck/Lint/AgentShield pass) and CodeRabbit approved at head. The only outstanding item is a cosmetic, non-blocking documentation nit (duplicate heading number).
Linked issue analysis
No GitHub-linked closing issues; PR references petry-projects/.github-private#817, #824, #825 (fleet-enablement initiative / S7-S8). The diff matches the stated intent: enroll petry-projects/.github in the idea→initiative pipeline via a thin caller stub and document the thin-stub→dispatch-reusable→central-planner architecture, the two human gates (idea:approved, initiative:auto), the hybrid project-board funnel, and the adoption runbook.
Findings
- minor (non-blocking): The added '### 10. Idea → Initiative pipeline' (line 973) duplicates the existing '### 10. PR Review Mention' (line 707). The file's section numbering is already inconsistent independent of this PR (two '### 8.' at lines 656/664; '### 9. Feature Ideation' at line 822 follows '### 11.' at line 735), so a clean fix means renumbering the conditional-workflow sections into one sequential scheme rather than only touching the new heading. Cosmetic, no functional/render impact — not a merge blocker for a docs+stub PR with green CI.
- info: GitHub Secret Protection MCP tool (run_secret_scanning) was not available in this environment; the secret scan relied on the gitleaks CI check (passed). No secrets present in the diff.
CI status
Green. SonarCloud, CodeQL, Lint, ShellCheck, Secret scan (gitleaks), AgentShield, Dependency-audit detect, and CodeRabbit all SUCCESS at head (3287e67). dev-lead dispatch/ci-relay jobs show CANCELLED (agent-dispatch jobs, non-gating); language-specific audit jobs SKIPPED as expected for this repo. mergeStateStatus is BLOCKED only pending code-owner (org-leads) approval.
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.
3 participants
Summary
Two things, both finishing the fleet-enablement initiative (
petry-projects/.github-private#817):Pilot enrollment (S8 #825): adopt the
initiative-plannercaller stub onpetry-projects/.githubitself. Onidea:approved(added by a trusted maintainer) it dispatches the central BMAD Scrum Master in.github-privatewith.githubastarget_repo, materializing an inert epic + story DAG here. This is the first end-to-end cross-repo validation of the fleet path (target_repo ≠ .github-private, writing viaGH_PAT_WORKFLOWS).Docs (S8 #825 / S7 #824):
ci-standards.md§10 documents the three caller stubs, the thin-stub→dispatch-reusable→central-planner architecture, the two human gates (idea:approved,initiative:auto), the hybrid board funnel (consumer repos → repo project;.github/.github-private→ org project Addressing PR comments #1), and the adoption runbook.Notes
idea:approvedlabel has been created on.github.initiative-planner/stablechannel (tag cut on release).idea:approvedto an Ideas Discussion → confirm an inertinitiativeepic appears in.github.Refs
petry-projects/.github-private#817,#824,#825🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Documentation