feat: implement issue #401 — Compliance: non-stub-pr-review-mention.yml - #407
Conversation
🤖 CodeAnt AI — Review Status
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
PR Summary by QodoPin pr-review-mention workflow to org reusable v2-stable channel
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR changes the reusable ChangesPR review mention workflow
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested labels: Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTo customize comments, go to the Qodo configuration screen, or learn more in the docs. |
There was a problem hiding this comment.
Code Review
This pull request updates the test suite in pr-review-mention-workflow.bats to verify that the workflow delegates to the major-scoped v2-stable channel instead of the bare stable channel, aligning with organization standards. There are no review comments, so I have no feedback to provide.
Dev-Lead — review-changes (no-changes)No changes were needed for this PR. |
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-07-31T15:32:30Z. |
donpetry-bot
left a comment
There was a problem hiding this comment.
Automated review — APPROVED ✓
Risk: MEDIUM
Reviewed commit: b30f068ce387193771de62ffc7c4277367c2f1c5
Review mode: triage-approved (single reviewer)
Summary
Compliance fix for #401: repins the pr-review-mention caller stub from the bare @pr-review-mention/stable tier to the major-scoped @pr-review-mention/v2-stable channel, and updates the bats guard to enforce the new pin. Verified the v2-stable tag exists in petry-projects/.github and the changed uses: line matches the canonical stub template verbatim.
Linked issue analysis
Issue #401 (compliance audit, ci-workflows/error) requires the caller workflow to pin the major-scoped channel @pr-review-mention/v-stable instead of the bare stable tier. The PR applies exactly this remediation: the uses: ref now matches standards/workflows/pr-review-mention.yml verbatim (verified via GitHub API), and the tag refs/tags/pr-review-mention/v2-stable exists (e0bb289). The bats delegation guard was updated in lockstep so drift back to the bare tier fails CI. Issue substantively addressed.
Findings
No blocking findings.
- The secrets block and permissions of the caller stub are unchanged; only the first-party channel ref moved, which complies with the org standard rather than deviating from it.
- run_secret_scanning MCP tool was not available in this environment; the gitleaks CI check passed and the diff contains no secret-like content.
- Advisory bots: Qodo (no issues), Gemini (no feedback), SonarCloud quality gate passed, AgentShield passed. CodeRabbit/Codex were rate-limited earlier; this is the post-window sweep re-review.
- Risk assessed MEDIUM (workflow-file change) — a minor uplift from triage's low-risk call, but the change is verified against the canonical template so triage's approval stands.
CI status
All substantive checks green: Lint, Format, Test, Secret scan (gitleaks), CodeQL, SonarCloud, AgentShield, dependency-audit. Two CANCELLED dev-lead jobs (run 30638701206) were superseded by a later successful run of the same workflow (30638580228). Mergeable; state BLOCKED only pending review approval.
Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.
|
|
Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-07-31T17:31:57Z. |



User description
Closes #401
Implemented by dev-lead agent. Please review.
CodeAnt-AI Description
Route pull request review mentions through the v2 stable workflow channel
What Changed
v2-stableworkflow channel instead of the previous stable channelImpact
✅ Consistent review mention handling✅ Protected pull request review triggers💡 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:
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
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:
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
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.
Summary by CodeRabbit