fix: pin dependabot-automerge reusable workflow to SHA

[don-petry]

Summary

• Pins petry-projects/.github/.github/workflows/dependabot-automerge-reusable.yml from @v1 to its commit SHA ee22b427cbce9ecadcf2b436acb57c3adf0cb63d # v1
• Satisfies the action-pinning policy

Closes #58.

Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 37 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b722b547-dcb1-412d-8647-c7f764cda80e

📥 Commits

Reviewing files that changed from the base of the PR and between 7d7648c and c09b166.

📒 Files selected for processing (1)

• .github/workflows/dependabot-automerge.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-58-20260418-1841

---

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]

Self-review

• Change is a single-line SHA pin: @v1 → @ee22b427cbce9ecadcf2b436acb57c3adf0cb63d # v1
• SHA verified via gh api repos/petry-projects/.github/git/refs/tags/v1 (type: commit — correct for Actions pinning)
• All other workflow structure (trigger, permissions, secrets: inherit) unchanged
• Matches the standards template at petry-projects/.github/standards/workflows/dependabot-automerge.yml with only the SHA substitution applied

No issues found.

---

@don-petry — CI is green, no review concerns. Ready for merge.

[Copilot]

Pull request overview

Pins the org-level Dependabot auto-merge reusable workflow reference to an immutable commit SHA to satisfy the repository’s action-pinning compliance policy (Issue #58).

Changes:

• Update .github/workflows/dependabot-automerge.yml to use petry-projects/.github/...@ee22b427cbce9ecadcf2b436acb57c3adf0cb63d # v1 instead of @v1.

---

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

[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

[donpetry-bot]

Superseded by automated re-review at ee6d1e18b6372f964e4c20d3aacbbcb84caa160f — click to expand prior review.

Review — fix requested (cycle 1/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.

[donpetry-bot]

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: ee6d1e18b6372f964e4c20d3aacbbcb84caa160f
Cascade: triage → deep (triage: haiku 4.5 → deep: sonnet 4.6 + duck: o4-mini → audit: opus 4.7)

Summary

This PR is a no-op: 0 changed files, 0 additions, 0 deletions. The compliance fix (SHA-pinning the reusable workflow ref) is already present in main — both branches are identical. CI is fully green (CodeQL, SonarQube, CodeRabbit all passed). The only blocker is a stale bot review whose findings section contains only the template placeholder '[Findings would be inserted here]', which should be dismissed as it represents a prior review-pipeline bug rather than a real finding.

Findings

• INFO: The PR diff is empty (0 changed files, 0 additions, 0 deletions). The target branch already contains the intended SHA-pin change. Merging this PR makes no modification to the repository.
• MINOR: The workflow file on main pins to SHA e6d47e0571ad88f1c4944be17da5b913dcc8c4e4 annotated '# v1', but the current v1 tag in petry-projects/.github resolves to d3d768dabb7f28cc63283cdfe48630da53700e50 (2026-05-13). The pinned commit (2026-05-15) is newer than v1 and the comment label is therefore inaccurate. This is a pre-existing issue in main and is not introduced by this PR.
• INFO: A prior automated review (cycle 1/3, SHA 0ba4043) posted a 'fix-requested' decision whose findings section is a verbatim template placeholder: '[Findings would be inserted here]'. This is a review-pipeline bug — no actual findings were generated. The review should be dismissed so the org-leads team can complete their required approval.
• INFO: All CI checks pass: CodeQL (SUCCESS), SonarQube Quality Gate (0 new issues, 0 security hotspots), CodeRabbit (SUCCESS).

---

Reviewed by the PR-review cascade (triage: haiku 4.5 → deep: sonnet 4.6 + duck: o4-mini → audit: opus 4.7). Reply if you need a human review.

[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