feat: add missing pr-review-mention.yml workflow

[don-petry]

Summary

• Adds .github/workflows/pr-review-mention.yml, a thin-caller stub copied verbatim from the org standard template at petry-projects/.github/standards/workflows/pr-review-mention.yml
• The stub delegates all logic to petry-projects/.github/.github/workflows/pr-review-mention-reusable.yml@v1
• No custom logic — this is a Tier 1 standard stub

Compliance

Resolves the compliance finding: Required workflow pr-review-mention.yml is missing (missing-pr-review-mention.yml check).

Closes #113

---

Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced CI/CD automation for pull request review workflows to improve development process efficiency.

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

[coderabbitai]

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 4 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7e8969b8-82aa-44a1-a80d-e8428403ddc1

📥 Commits

Reviewing files that changed from the base of the PR and between 7d37bda and 5bcbd55.

📒 Files selected for processing (1)

• .github/workflows/pr-review-mention.yml

📝 Walkthrough

Walkthrough

A new GitHub Actions workflow .github/workflows/pr-review-mention.yml is added to delegate PR review mention handling to the organization's reusable workflow. The workflow triggers on pull request review requests, issue comments, and pull request review comments with minimum required permissions.

Changes

PR Review Mention Workflow

Layer / File(s)	Summary
Workflow configuration and reusable delegation .github/workflows/pr-review-mention.yml	Introduces the pr-review-mention workflow that triggers on issue_comment, pull_request_review_comment, and pull_request review-requested events. Enforces empty top-level permissions and configures the job with pull-requests: write permission while delegating to pr-review-mention-reusable.yml@v1 with secrets: inherit.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Fix org-wide failure of pr-review-mention reusable workflow caller (stale v1 tag) .github#267: The PR adds a pinned reusable workflow reference (@v1), directly addressing stale tag issues in org workflow callers.
• Compliance: non-stub-pr-review-mention.yml ContentTwin#144: The PR adds the compliant stub pr-review-mention.yml workflow, resolving the compliance gap for unpinned or missing PR review mention handling.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title directly describes the main change: adding the missing pr-review-mention.yml workflow file, which is the primary objective of the changeset.
Linked Issues check	✅ Passed	The pull request successfully addresses the compliance requirement in issue #113 by adding the required pr-review-mention.yml workflow file as a thin-caller stub.
Out of Scope Changes check	✅ Passed	All changes are directly related to resolving issue #113; the pull request only adds the required workflow file with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-113-20260511-2018

---

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 and usage tips.}

[don-petry]

@petry-projects/org-leads — PR is ready for review and merge. This is a verbatim copy of the org standard template for pr-review-mention.yml, resolving the compliance finding in #113.

[Copilot]

Pull request overview

Adds the missing Tier 1 “thin-caller” workflow required by org CI standards, delegating PR-review mention handling to the centralized reusable workflow.

Changes:

• Introduces .github/workflows/pr-review-mention.yml as a thin-caller stub.
• Configures mention/review-request triggers and delegates execution to petry-projects/.github/.github/workflows/pr-review-mention-reusable.yml@v1.
• Uses secrets: inherit and a minimal job-level permissions block consistent with other stubs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[donpetry-bot]

Automated review — APPROVED ✓

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

Summary

This PR adds .github/workflows/pr-review-mention.yml as a Tier 1 thin-caller stub, copied verbatim from the org standard template at petry-projects/.github/standards/workflows/pr-review-mention.yml. The stub delegates all logic to the pinned reusable workflow petry-projects/.github/.github/workflows/pr-review-mention-reusable.yml@v1. No custom logic is introduced. Confirming the triage assessment: this is a low-risk compliance fix.

Linked issue analysis

Closes #113 — Compliance: missing-pr-review-mention.yml. The compliance finding required adding this exact workflow per standards/ci-standards.md#required-workflows. The PR adds the workflow at the required path with the standard contents, fully addressing the finding.

Findings

• Permissions hygiene: ✅ Top-level permissions: {} is empty; the job grants only pull-requests: write, which is the minimum the reusable workflow needs.
• Pinned reusable: ✅ The uses: reference is pinned to @v1, matching the org standard.
• Triggers: ✅ issue_comment, pull_request_review_comment, and pull_request: [review_requested] match the standard template and are appropriate for mention-trigger handling. Note that issue_comment and pull_request_review_comment fire on comments from any user — the privileged logic is centralized in the org reusable, which is the correct place to enforce authorization.
• secrets: inherit: ✅ Required by the standard pattern so the reusable can access GH_PAT_WORKFLOWS. This is the documented and expected approach for org-standard thin callers.
• SonarQube Security Hotspots: Informational only (the SonarQube check is not part of the blocking status rollup). These are typical advisories for reusable-workflow caller patterns and match the org-approved baseline.
• Diff: +38/-0, single file added. Matches the org template byte-for-byte based on the header comment block.

CI status

• CodeQL Analyze (actions): SUCCESS
• CodeQL: SUCCESS
• CodeRabbit: SUCCESS (approved review at head SHA)
• Mergeable state: BLOCKED only on required human approval; no failing checks.

---

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

[sonarqubecloud]

Quality Gate failed

Failed conditions
2 Security Hotspots

See analysis details on SonarQube Cloud

[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]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[donpetry-bot]

Review — fix requested (cycle 2/3)

The automated review identified the following issues. Please address each one:

Findings to fix

[Findings would be inserted here]

Additional tasks

1. Resolve all unresolved review thread comments from other reviewers
2. Ensure all CI checks pass after your changes
3. Rebase on the target branch if behind
4. Do NOT modify files unrelated to the findings above

The review cascade will automatically re-review after new commits are pushed.

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

[don-petry]

Rebase complete — branch rebased onto `main` (commit `a0ef82a`).

All 6 unique PR commits were either already absorbed by main or superseded:

• pr-review-mention.yml: PR added `@v1` stub; main already had `@v2` with explicit secrets — kept main's version.
• pr_review_health.sh (modify/delete): PR refactored it; main replaced it entirely with `fleet_monitor.sh` — accepted deletion.
• daily-pr-review-health.yml (modify/delete): PR dropped Node/Claude steps; main renamed the workflow to `actions-fleet-monitor.yml` — accepted deletion.
• actions-fleet-monitor.yml: PR had simpler version using `pr_review_health.sh`; main has full org-wide fleet monitor version — kept main's version.
• rename commits (×2): Detected as already-upstream and dropped automatically.

The branch now has zero net diff against `main` — all work from this PR has been incorporated into main through prior merges.

[don-petry]

No description provided.