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

[don-petry]

User description

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.

---

CodeAnt-AI Description

Update the project-add workflow stub to the v1 stable channel

What Changed

• The project-add workflow now points to the add-to-project/v1-stable channel instead of the older stable channel
• The workflow continues to use the same project settings and approved secrets
• A trailing newline was added at the end of the file

Impact

✅ Keeps project auto-adds on the current supported workflow channel
✅ Reduces the risk of drift from the shared workflow standard
✅ Preserves existing project setup and secret handling

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	b331c8c	Jul 22, 2026 · 04:11	04:12

_{Updated in place by CodeAnt AI · last 5 reviews}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 6 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 28bb4cc5-75c5-47f2-b6c5-5f5afa75b2ce

📥 Commits

Reviewing files that changed from the base of the PR and between 7faff8e and b331c8c.

📒 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-20260722

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

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

No changes were needed for this PR.

[donpetry-bot]

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-07-22T05:14:57Z.

[donpetry-bot]

Automated review — APPROVED ✓

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

Summary

Verbatim org-standards sync (3 lines) updating the add-to-project workflow stub's channel ref from add-to-project/stable to add-to-project/v1-stable, plus a trailing-newline fix. Verified against the source of truth: the stub is byte-identical to standards/workflows/add-to-project.yml in petry-projects/.github, the add-to-project/v1-stable tag exists, and the reusable workflow file exists at that tag. Triggers, concurrency, permissions (contents: read), and the explicit secrets mapping are unchanged.

Linked issue analysis

No linked issues. This is an automated standards-sync PR opened by scripts/deploy-standard-workflows.sh; no issue linkage is expected.

Findings

• Confirms triage assessment: mechanical, first-party channel-ref bump deployed verbatim from the org standards repo — no logic, permission, trigger, or secret-handling changes.
• Channel ref target verified: tag add-to-project/v1-stable exists in petry-projects/.github and contains add-to-project-reusable.yml. Channel refs (not SHAs) are the documented standard for these first-party stubs per ci-standards.md; NOSONAR annotation carried over correctly.
• Secrets: only a trailing newline touched the secrets block; explicit per-secret mapping preserved (no secrets: inherit). No secret material in the diff; gitleaks CI passed. MCP secret-scanning tool not available in this run — noted, non-blocking.
• Advisory-bot note: gemini/codex/coderabbit were rate-limited at PR open (a prior rate-limited marker deferred auto-approval), but CodeAnt completed a full review and SonarCloud quality gate passed with 0 issues — sufficient coverage for a verbatim 3-line sync.

CI status

All checks green: CI (Go, TypeScript, gitleaks), CodeQL (go, javascript-typescript, actions), SonarCloud quality gate passed (0 new issues, 0 hotspots), AgentShield, dependency-audit (govulncheck, pnpm audit). Remaining checks skipped as not applicable. Mergeable; blocked only on review approval.

---

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