[don-petry]

User description

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

• pr-auto-review.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.

Summary by CodeRabbit

• Documentation
  • Clarified that the CI workflow reference should be replaced with the repository’s actual workflow name(s).

---

CodeAnt-AI Description

Clarify how to configure the pull request review workflow for each repository

What Changed

• Replaces the repository-specific workflow comment with a clear reminder to set the CI workflow name or names for the current repository

Impact

✅ Clearer CI workflow configuration

💡 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.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Incremental review completed	6368af2	Aug 14, 2026 · 14:46	14:46
✅ Reviewed your PR	9a1e13b	Aug 10, 2026 · 09:39	09:40

[chatgpt-codex-connector]

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

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[gemini-code-assist]

Note

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

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates one comment in the pull request auto-review workflow. The comment now tells maintainers to replace "CI" with the repository’s workflow name or names.

Changes

Workflow comment clarification

Layer / File(s)	Summary
Customize workflow name instruction .github/workflows/pr-auto-review.yml	The comment now instructs maintainers to customize the workflow name or names instead of treating "CI" as a fixed repository workflow name.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• petry-projects/markets#393: Modifies the same workflow comment and the description of the "CI" placeholder.

Suggested reviewers: donpetry-bot

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes syncing an organization-standard workflow stub into the repository.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch standards-sync/workflows-20260810

---

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.}

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
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 — waiting on PR blockers (intent: review-changes)

PR: #412
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-08-14T15:19:10Z

[don-petry]

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-08-14T15:19:10Z

[donpetry-bot]

Automated review — APPROVED ✓

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

Summary

Standards-sync PR deploying the org-standard pr-auto-review.yml stub verbatim from petry-projects/.github (standards/workflows/). The diff is a single comment-line change (+1/−1): the repo-specific note "CI" matches this repository's CI workflow name is replaced by the generic upstream comment TODO: replace "CI" with your repository's CI workflow name(s). I verified the new line matches the org-standard source file byte-for-byte, and the functional trigger config (workflows: ["CI"]) is unchanged and remains correct — this repo's CI workflow is named "CI". No behavioral change whatsoever.

Linked issue analysis

No linked issues. This is an automated standards-sync PR opened by scripts/deploy-standard-workflows.sh, which does not require a linked issue per org convention (labeled standards-sync).

Findings

• Comment-only change to a thin-caller workflow stub; no change to triggers, permissions, secrets, or called reusables.
• Verified verbatim match against the source of truth at petry-projects/.github:standards/workflows/pr-auto-review.yml.
• Minor (non-blocking): the generic upstream TODO comment is already satisfied in this repo (the CI workflow is named "CI"), so the comment is slightly less informative than the line it replaces — an accepted consequence of verbatim stub deployment. This is also the likely source of SonarCloud's 1 new (non-blocking) issue, since Sonar flags TODO comments; the quality gate still passed.
• Secret scan: run_secret_scanning MCP tool not available in this environment; gitleaks CI check passed and the diff contains no secret material.
• Triage assessment (low-risk) confirmed correct.

CI status

All required checks green: CI (Detect ecosystems, gitleaks secret scan — SUCCESS; Backend/Frontend CI skipped, no matching changes), CodeQL (actions) SUCCESS, SonarCloud quality gate passed, AgentShield SUCCESS, CodeRabbit SUCCESS, dependency-audit SUCCESS/skipped. The only non-success entry is a CANCELLED review / review run of the PR Review Agent workflow itself — a superseded prior run of this review pipeline, not a CI failure.

---

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