Skip to content

chore: sync 1 org-standard workflow stub(s) from petry-projects/.github - #1190

Merged
don-petry merged 1 commit into
mainfrom
standards-sync/workflows-20260713
Jul 13, 2026
Merged

don-petry merged 1 commit into
mainfrom
standards-sync/workflows-20260713

Conversation

@don-petry

Copy link
Copy Markdown
Collaborator

Syncs the following org-standard workflow stub(s) from petry-projects/.github (standards/workflows/), deployed verbatim:

  • add-to-project.yml

Opened by scripts/deploy-standard-workflows.sh. Stubs are thin callers; all behaviour lives in the reusables. See standards/ci-standards.md. Labeled standards-sync and left for the normal review/auto-merge pipeline — the deploy script never merges directly.

@don-petry
don-petry requested a review from a team as a code owner July 13, 2026 11:37
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@don-petry, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e3e51f12-4b83-4a7a-ba9f-268522f491bd

📥 Commits

Reviewing files that changed from the base of the PR and between 2400dd8 and 5cbe19a.

📒 Files selected for processing (1)
  • .github/workflows/add-to-project.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch standards-sync/workflows-20260713

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry
don-petry enabled auto-merge (squash) July 13, 2026 11:38
@sonarqubecloud

Copy link
Copy Markdown

@don-petry
don-petry disabled auto-merge July 13, 2026 11:39
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 0
- Quality Gate passed with 0 new issues — no actionable items
Files changed: (none — no code issues identified)
Skipped (informational): 0
```
The PR is in good standing. All automated quality checks pass, and the SonarCloud analysis found no new issues.

@don-petry
don-petry enabled auto-merge (squash) July 13, 2026 11:39
@donpetry-bot

Copy link
Copy Markdown
Contributor

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-07-13T12:40:04Z.

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: 5cbe19a0369336c91db9f7e6db3a2907a5705704
Review mode: triage-approved (single reviewer)

Summary

Automated standards-sync PR updating the add-to-project.yml thin caller stub (+6/−10, 1 file). Verified byte-for-byte identical to the upstream source at petry-projects/.github standards/workflows/add-to-project.yml. Changes: removes the discussion trigger (Ideas no longer tracked here), simplifies the concurrency group accordingly, and promotes the reusable workflow ref from the add-to-project/next channel to add-to-project/stable. Triage assessment (low-risk) confirmed.

Linked issue analysis

No linked issues — this is an automated standards-sync PR opened by scripts/deploy-standard-workflows.sh. Tracking references (combsmith/.github#387, #415) are documented in the stub header. N/A.

Findings

No blocking findings.

  • Verbatim deployment confirmed: the PR file is identical to standards/workflows/add-to-project.yml in petry-projects/.github, per the thin-caller policy in AGENTS.md/CLAUDE.md.
  • Security surface reduced, not increased: the discussion trigger is removed; permissions: {} at top level and contents: read on the job are unchanged. The pre-existing pull_request_target trigger delegates all behaviour to the first-party reusable. The channel-branch ref (add-to-project/stable, not SHA-pinned) is the org-accepted first-party pattern, explicitly annotated NOSONAR, and moving next→stable is a hardening step.
  • Secret scan: the run_secret_scanning MCP tool was not available in this run; the gitleaks CI check passed and the diff contains no secret-like content.
  • Advisory bots rate-limited: Codex and CodeRabbit incremental reviews were rate-limited (prior sweep posted a hold, reset 2026-07-13T12:40:04Z). CodeRabbit's commit status is SUCCESS and independent analyzers (SonarCloud quality gate, CodeQL actions+python, actionlint/ShellCheck, agent security scan) all passed, so this single-reviewer confirmation in triage-approved mode proceeds on those signals.

CI status

All required checks green: CI (Lint, ShellCheck, secret scan, agent security scan, compile), CodeQL (actions, python), SonarCloud quality gate passed (0 new issues, 0 hotspots), Tests (unit-tests, bats), Lint (shellcheck, template-drift, gh-aw-compile, validate-agent-profiles), Holdout Guard, AgentShield, Test-Deletion Guard. One early guard run shows CANCELLED but was superseded by a successful run of the same check. Dependency-audit sub-checks SKIPPED (no matching ecosystems). mergeable=MERGEABLE; mergeStateStatus=BLOCKED only pending review.


Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

@don-petry
don-petry merged commit 67ec50f into main Jul 13, 2026
32 of 33 checks passed
@don-petry
don-petry deleted the standards-sync/workflows-20260713 branch July 13, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants