Add permission to coderabbit retry top workflow

[greenscientist]

Summary by CodeRabbit

• Chores
  • Updated automated workflow configuration to explicitly grant the required permissions for pull request retry actions.
  • Continued delegating execution to the shared retry workflow while securely inheriting the needed secrets.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 8 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 Plus

Run ID: 59cc640a-ec2d-45d7-8a03-778326468bef

📥 Commits

Reviewing files that changed from the base of the PR and between e3f34a7 and c7a0538.

📒 Files selected for processing (1)

• .github/workflows/coderabbit-retry.yml

Walkthrough

The retry job now explicitly grants pull-requests: write and contents: read permissions while invoking the delegated retry workflow with inherited secrets.

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

Possibly related PRs

• chairemobilite/trRouting#354: Modifies the same retry workflow.
• chairemobilite/trRouting#359: Adds the same explicit permissions to the retry workflow.

🚥 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 title clearly describes the main change: adding permissions to the coderabbit retry top workflow.
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.

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/coderabbit-retry.yml:
- Around line 16-17: Update the reusable workflow reference in the scheduled
workflow to use a reviewed, immutable commit SHA instead of the mutable `@main`
branch, while preserving the existing inherited secrets and permissions
configuration.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: fe76d72e-c616-4ad5-8261-ff001f878f4c

📥 Commits

Reviewing files that changed from the base of the PR and between e52ebef and 0748331.

📒 Files selected for processing (1)

• .github/workflows/coderabbit-retry.yml

📜 Review details

⏰ Context from checks skipped due to timeout. (6)

• GitHub Check: Analyze (cpp)
• GitHub Check: pr-build-check
• GitHub Check: Test build on macOS-latest (memcached: false)
• GitHub Check: Test build on macOS-latest (memcached: true)
• GitHub Check: Test build on ubuntu-latest (memcached: true)
• GitHub Check: Test build on ubuntu-latest (memcached: false)

🧰 Additional context used

🪛 zizmor (1.26.1)

.github/workflows/coderabbit-retry.yml

[error] 16-16: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)

---

[warning] 15-15: permissions without explanatory comments (undocumented-permissions): needs an explanatory comment

(undocumented-permissions)

---

[warning] 16-16: secrets unconditionally inherited by called workflow (secrets-inherit): this reusable workflow

(secrets-inherit)

🔇 Additional comments (1)

.github/workflows/coderabbit-retry.yml (1)

14-17: 🎯 Functional Correctness

Verify the delegated workflow’s permission contract.

This job-level permissions block sets every unspecified scope to none. Confirm the called workflow does not require contents: read or another omitted scope; otherwise retries may fail at runtime.

[coderabbitai]

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow files =="
git ls-files .github/workflows | sed -n '1,120p'

echo
echo "== target file =="
if [ -f .github/workflows/coderabbit-retry.yml ]; then
  cat -n .github/workflows/coderabbit-retry.yml | sed -n '1,120p'
else
  echo "target not found"
fi

echo
echo "== reusable workflow references in workflows =="
rg -n "uses: chairemobilite/transition/.github/workflows/coderabbit-retry.yml|permissions:|pull-requests:\s*write|secrets:\s*inherit|pull_request" .github/workflows || true

Repository: chairemobilite/trRouting

Length of output: 1537

---

Pin the reusable workflow before granting it secrets and write access.

This scheduled workflow calls a mutable @main reusable workflow with inherited secrets and pull-requests: write. Pin the workflow to a reviewed commit SHA instead.

🧰 Tools

🪛 zizmor (1.26.1)

[error] 16-16: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)

---

[warning] 16-16: secrets unconditionally inherited by called workflow (secrets-inherit): this reusable workflow

(secrets-inherit)

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/coderabbit-retry.yml around lines 16 - 17, Update the
reusable workflow reference in the scheduled workflow to use a reviewed,
immutable commit SHA instead of the mutable `@main` branch, while preserving the
existing inherited secrets and permissions configuration.

Source: Linters/SAST tools

[github-actions]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[greenscientist]

@kaligrafy This should mostly fix the problem with the PR update bot, but still not 100% convinced. Seem better