fix(ci): pin claude-code-reusable.yml ref to @v1 by don-petry · Pull Request #218 · petry-projects/.github

don-petry · 2026-05-08T17:34:02Z

Summary

Copies .github/workflows/claude.yml verbatim from the org-level template (standards/workflows/claude.yml)
Changes uses: petry-projects/.github/.github/workflows/claude-code-reusable.yml@main → @v1 — internal reusable workflow refs use a version tag, not a branch ref, per the Action Pinning Policy in ci-standards.md
Adds paths-ignore OIDC guard on pull_request trigger (prevents 401 token-exchange failures when this file itself is the only change in a PR)
Adds canonical header comment block from the template

Why not SHA-pin?

Per ci-standards.md §Action Pinning Policy, internal reusable workflow refs (petry-projects/.github/.github/workflows/*) are exempt from SHA-pinning. The @v1 tag is the correct, stable reference. SHA-pinning this line would break OIDC token validation.

Test plan

CI passes on this PR
Compliance audit no longer flags claude.yml as having an unpinned action

Closes #105

Generated with Claude Code

Summary by CodeRabbit

Chores
- Updated CI/CD workflow configuration to use a stable version reference, improving release consistency and reliability.

coderabbitai · 2026-05-08T17:34:09Z

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minute and 31 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: 23a485cf-061f-4a29-9cb9-172bc83e8000

📥 Commits

Reviewing files that changed from the base of the PR and between 3c0c38f and 9444491.

📒 Files selected for processing (1)

.github/workflows/claude.yml

📝 Walkthrough

Walkthrough

The .github/workflows/claude.yml file is updated to pin its reusable workflow reference from @main to the stable @v1 tag. All other workflow structure, permissions, and secrets inheritance remain unchanged. This single-line change addresses the action-pinning compliance requirement.

Changes

Workflow Reference Pinning

Layer / File(s)	Summary
Workflow Reference Update `.github/workflows/claude.yml`	Reusable workflow `uses:` reference changed from `petry-projects/.github/.github/workflows/claude-code-reusable.yml@main` to `@v1` tag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

Compliance: unpinned-actions-claude.yml #105: This PR directly resolves the compliance finding flagged by this issue—the change pins the reusable workflow reference to @v1 instead of the unpinned @main branch, satisfying the action-pinning policy requirement.

Possibly related PRs

petry-projects/.github#77: Earlier PR that introduced the reusable workflow delegation pattern in claude.yml; this PR pins that reference to stable @v1.
petry-projects/.github#159: Documents and validates the use of @v1 for reusable workflow references, providing the stability framework this PR implements.
petry-projects/.github#89: Adds audit enforcement that workflows must reference reusable workflows with @v1, which this PR satisfies.

🚥 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 accurately describes the main change: pinning the claude-code-reusable.yml workflow reference from `@main` to `@v1`.
Linked Issues check	✅ Passed	The PR successfully addresses issue `#105` by changing the reusable workflow reference from `@main` to `@v1`, which complies with the action pinning policy for internal reusable workflows.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly related to issue `#105`: updating the workflow reference to comply with action pinning policy; no unrelated modifications detected.
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-105-20260508-1731

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

don-petry · 2026-05-08T17:36:04Z

@petry-projects/org-leads — this PR is ready for review and merge. All required CI checks pass. It fixes the compliance finding by copying .github/workflows/claude.yml verbatim from the org template, changing @main → @v1 on the reusable workflow ref (internal refs use version tags, not branches, per ci-standards.md).

Copilot

Pull request overview

Updates the repository’s claude.yml Tier-1 workflow stub to match the org standard template and switch the reusable workflow reference from a branch ref (@main) to a version tag (@v1).

Changes:

Adds the canonical “SOURCE OF TRUTH” header block from standards/workflows/claude.yml.
Adds paths-ignore on the pull_request trigger for .github/workflows/claude.yml.
Changes reusable workflow reference from claude-code-reusable.yml@main to @v1.

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

The merge-base changed after approval.

github-actions · 2026-05-12T03:02:48Z

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

Please resolve the conflicts and push:

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

@main

Copies claude.yml verbatim from the org standards template (standards/workflows/claude.yml). Key changes: - @main → @v1 (internal reusable refs use tag, not branch, per ci-standards.md) - Add paths-ignore OIDC guard on pull_request trigger - Add canonical header comment block from template Closes #105 Co-authored-by: Don Petry <don-petry@users.noreply.github.com>

donpetry-bot · 2026-05-13T23:17:32Z

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

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

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

don-petry · 2026-05-17T10:41:11Z

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 · 2026-05-17T11:31:03Z

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 · 2026-05-17T12:04:33Z

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 · 2026-05-17T12:59:05Z

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 · 2026-05-17T14:27:26Z

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 · 2026-05-17T15:25:07Z

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 · 2026-05-17T15:59:21Z

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 · 2026-05-17T16:26:47Z

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

dev-lead 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 · 2026-05-17T17:20:38Z

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

dev-lead 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 · 2026-05-18T17:02:38Z

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

dev-lead 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 · 2026-05-19T01:35:06Z

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

dev-lead 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 · 2026-05-19T11:58:38Z

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

dev-lead 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 · 2026-05-20T01:31:10Z

@dev-lead - please fix this PR

don-petry · 2026-05-20T19:27:29Z

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

dev-lead 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 · 2026-05-21T00:03:02Z

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

dev-lead 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 · 2026-05-21T12:17:28Z

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

dev-lead 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 · 2026-05-21T12:20:56Z

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

dev-lead 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 · 2026-05-21T13:01:19Z

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

dev-lead 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 · 2026-05-21T19:47:17Z

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

dev-lead 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 · 2026-05-24T00:23:41Z

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

dev-lead 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 · 2026-05-24T09:53:16Z

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

dev-lead 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 · 2026-05-24T13:23:22Z

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

dev-lead 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 · 2026-05-24T13:27:53Z

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

dev-lead 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 · 2026-05-26T17:03:47Z

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

dev-lead 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 · 2026-05-31T10:15:28Z

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

dev-lead 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 · 2026-05-31T10:19:39Z

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

dev-lead 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

Copilot AI review requested due to automatic review settings May 8, 2026 17:34

don-petry requested a review from a team as a code owner May 8, 2026 17:34

don-petry mentioned this pull request May 8, 2026

Compliance: unpinned-actions-claude.yml #105

Closed

Copilot started reviewing on behalf of don-petry May 8, 2026 17:34 View session

Copilot AI reviewed May 8, 2026

View reviewed changes

Comment thread .github/workflows/claude.yml

Comment thread .github/workflows/claude.yml

don-petry mentioned this pull request May 9, 2026

Org Status — 2026-05-09 #225

Closed

coderabbitai Bot previously approved these changes May 10, 2026

View reviewed changes

don-petry mentioned this pull request May 10, 2026

Org Status — 2026-05-10 #233

Closed

don-petry closed this May 11, 2026

don-petry reopened this May 11, 2026

don-petry closed this May 12, 2026

don-petry reopened this May 12, 2026

don-petry enabled auto-merge (squash) May 12, 2026 01:42

don-petry force-pushed the main branch from 3403601 to 767bfec Compare May 12, 2026 02:50

don-petry force-pushed the claude/issue-105-20260508-1731 branch from 3b75354 to bc19560 Compare May 13, 2026 16:55

Merge branch 'main' into claude/issue-105-20260508-1731

21a39ff

This was referenced May 13, 2026

Org Status — 2026-05-13 #284

Closed

Org Status — 2026-05-13 #285

Closed

Merge branch 'main' into claude/issue-105-20260508-1731

1f4a05c

don-petry mentioned this pull request May 14, 2026

Org Status — 2026-05-14 #286

Closed

don-petry added 4 commits May 14, 2026 10:13

Merge branch 'main' into claude/issue-105-20260508-1731

5addb4e

Merge branch 'main' into claude/issue-105-20260508-1731

cb9861e

Merge branch 'main' into claude/issue-105-20260508-1731

23e80fd

Merge branch 'main' into claude/issue-105-20260508-1731

b9092f2

don-petry mentioned this pull request May 19, 2026

Org Status — 2026-05-19 #325

Closed

don-petry mentioned this pull request May 21, 2026

Org Status — 2026-05-21 #333

Closed

This was referenced May 25, 2026

Org Status — 2026-05-25 #351

Closed

Org Status — 2026-05-26 #352

Closed

Conversation

don-petry commented May 8, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Why not SHA-pin?

Test plan

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented May 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Rate limit exceeded

Walkthrough

Changes

Estimated code review effort

Possibly related issues

Possibly related PRs

Uh oh!

don-petry commented May 8, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

github-actions Bot commented May 12, 2026

Uh oh!

donpetry-bot commented May 13, 2026

Review — fix requested (cycle 1/3)

Findings to fix

Additional tasks

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 17, 2026

Uh oh!

don-petry commented May 18, 2026

Uh oh!

don-petry commented May 19, 2026

Uh oh!

don-petry commented May 19, 2026

Uh oh!

don-petry commented May 20, 2026

Uh oh!

don-petry commented May 20, 2026

Uh oh!

don-petry commented May 21, 2026

Uh oh!

don-petry commented May 21, 2026

Uh oh!

don-petry commented May 21, 2026

Uh oh!

don-petry commented May 21, 2026

Uh oh!

don-petry commented May 21, 2026

Uh oh!

don-petry commented May 24, 2026

Uh oh!

don-petry commented May 24, 2026

Uh oh!

don-petry commented May 24, 2026

Uh oh!

don-petry commented May 24, 2026

Uh oh!

don-petry commented May 26, 2026

Uh oh!

don-petry commented May 8, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 8, 2026 •

edited

Loading