chore: sync 1 org-standard workflow stub(s) from petry-projects/.github - #468
Conversation
don-petry
added
the
standards-sync
don-petry
added
the
standards-sync
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Warning Review limit reached
Next review available in: 34 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
There was a problem hiding this comment.
Pull request overview
Adds the org-standard Initiative Driver GitHub Actions workflow stub to this repository. This workflow is a thin dispatcher that triggers the centralized initiative-driver.yml in petry-projects/.github-private, allowing the central driver to sweep this repo’s initiative:auto epics without each repo running the full driver logic.
Changes:
- Add
.github/workflows/initiative-driver.ymldispatcher workflow triggered onissuesclose/label events, schedule, and manual dispatch. - Add a PAT guard and
gh workflow rundispatch to the central driver withtarget_repo=${{ github.repository }}.
| # 3. Confirm the org-level secret GH_PAT_WORKFLOWS is accessible **and its | ||
| # owner has write access to petry-projects/.github-private** (to dispatch | ||
| # the central workflow) **and to this repo** (the central driver applies the | ||
| # `dev-lead` label cross-repo with that PAT; a label applied with | ||
| # GITHUB_TOKEN would not trigger dev-lead). |
There was a problem hiding this comment.
Fixed in .github/workflows/initiative-driver.yml: removed the secrets.GH_PAT_DON_PETRY || fallback from both GH_TOKEN expressions, so the only accepted secret is now GH_PAT_WORKFLOWS — matching what the adoption notes in the header already document. Operators following the adoption steps will no longer be misled.
| GH_TOKEN: ${{ secrets.GH_PAT_DON_PETRY || secrets.GH_PAT_WORKFLOWS }} | ||
| run: | | ||
| if [ -z "${GH_TOKEN}" ]; then | ||
| echo "::error::GH_PAT_WORKFLOWS is required — a workflow_dispatch fired with GITHUB_TOKEN never starts a run." |
There was a problem hiding this comment.
Fixed alongside the thread above: both GH_TOKEN env expressions now use only secrets.GH_PAT_WORKFLOWS (no GH_PAT_DON_PETRY fallback), so the guard error message — GH_PAT_WORKFLOWS is required — is now accurate and matches the actual requirement.
| schedule: | ||
| - cron: "41 3 * * *" # off-peak safety net for missed close events | ||
| workflow_dispatch: |
There was a problem hiding this comment.
Added .github/workflows/initiative-driver.yml to .prettierignore (option b), following the same pattern already used for dev-lead.yml. This prevents Prettier from reformatting the file on future syncs and eliminates the risk of byte-drift from the org source of truth.
Fixed cron expression quote style to comply with Prettier. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Dev-Lead — fix-bot-comment (applied)Changes committed and pushed. |
Dev-Lead — review-changes (applied)Changes committed and pushed. |
|
Syncs the following org-standard workflow stub(s) from
petry-projects/.github(standards/workflows/), deployed verbatim:initiative-driver.ymlOpened by
scripts/deploy-standard-workflows.sh. Stubs are thin callers; all behaviour lives in the reusables. Seestandards/ci-standards.md. Labeledstandards-syncand left for the normal review/auto-merge pipeline — the deploy script never merges directly.