Skip to content

chore: remove deprecated claude.yml from standards#379

Open
don-petry wants to merge 4 commits into
mainfrom
chore/remove-deprecated-claude-yml
Open

chore: remove deprecated claude.yml from standards#379
don-petry wants to merge 4 commits into
mainfrom
chore/remove-deprecated-claude-yml

Conversation

@don-petry
Copy link
Copy Markdown
Contributor

@don-petry don-petry commented May 30, 2026

The claude.yml workflow template has been deprecated in favor of dev-lead.yml as the standard workflow for all org repos (ref: PR #301).

All org repos have migrated to dev-lead.yml. This removes the obsolete template from the org-level standards directory and workflow template catalog.

Summary by CodeRabbit

  • Chores
    • Removed a workflow automation configuration that previously delegated processing tasks triggered by repository events.

don-petry and others added 2 commits May 18, 2026 11:57
Add a concurrency block to both the live dev-lead.yml and the
standards/workflows/dev-lead.yml template so that at most one dev-lead
dispatch run executes per repo at a time (ci-relay retains its ephemeral
per-SHA slot). Matches the policy landed in .github-private.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
The claude.yml workflow template has been deprecated in favor of dev-lead.yml
as the standard workflow for all org repos (PR #301).

All repos have migrated to dev-lead.yml. This removes the obsolete template
from the org-level standards directory.
Copilot AI review requested due to automatic review settings May 30, 2026 14:10
@don-petry don-petry requested a review from a team as a code owner May 30, 2026 14:10
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 30, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 282d6c03-24b1-4fd1-8902-23ddfe724d14

📥 Commits

Reviewing files that changed from the base of the PR and between bf65972 and 87f9c4c.

📒 Files selected for processing (1)
  • standards/workflows/claude.yml
💤 Files with no reviewable changes (1)
  • standards/workflows/claude.yml

📝 Walkthrough

Walkthrough

The PR removes standards/workflows/claude.yml, a workflow file that previously delegated Claude Code triggers (PR, issue, comment, check_run events) to the organization's upstream reusable workflow. With this deletion, those event-driven triggers and the reusable-workflow delegation are no longer defined in this repository.

Changes

Cohort / File(s) Summary
Workflow file removal
standards/workflows/claude.yml
Deletes the Claude Code workflow that delegated PR/issue/comment/check_run triggers to petry-projects/.github/.github/workflows/claude-code-reusable.yml@v1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • petry-projects/.github#321: Deletes the reusable Claude Code workflow definition and updates related dev-lead sentinel references, coordinating with this PR's removal of the local workflow caller.
  • petry-projects/.github#301: Decommissions the Claude Code workflow as part of a broader transition to the dev-lead workflow standard.
🚥 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—removal of the deprecated claude.yml workflow—and aligns with the primary commit's intent, though it does not reflect the secondary concurrency change also included in the PR.
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.

✏️ 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 chore/remove-deprecated-claude-yml

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.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes a workflow file and introduces a concurrency configuration to the dev-lead.yml workflow. A review comment suggests scoping the concurrency group to specific pull requests or issues rather than using a single global group, which would otherwise block concurrent workflow runs across different pull requests in the repository.

Comment on lines +40 to +48
concurrency:
# One active run per repo; ci-relay (check_run) keeps an ephemeral per-SHA slot
# so it can fire immediately without blocking or being blocked by the dispatch queue.
group: >-
${{
github.event_name == 'check_run' && format('dev-lead-ci-relay-{0}', github.event.check_run.head_sha) ||
'dev-lead'
}}
cancel-in-progress: false
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Using a single global 'dev-lead' concurrency group for all non-check_run events means that any activity (such as comments, reviews, or pushes) on one pull request or issue will block the agent from running on all other pull requests or issues in the repository. This can lead to significant delays and a poor developer experience in active repositories.

We can scope the concurrency group to the specific pull request or issue using github.event.pull_request.number or github.event.issue.number, falling back to 'global' only when neither is available (e.g., for repository dispatches).

concurrency:
  # One active run per PR/issue; ci-relay (check_run) keeps an ephemeral per-SHA slot
  # so it can fire immediately without blocking or being blocked by the dispatch queue.
  group: >-
    ${
      github.event_name == 'check_run' && format('dev-lead-ci-relay-{0}', github.event.check_run.head_sha) ||
      format('dev-lead-{0}', github.event.pull_request.number || github.event.issue.number || 'global')
    }}
  cancel-in-progress: false

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 77bd0c1b04

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -1,68 +0,0 @@
# ─────────────────────────────────────────────────────────────────────────────
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove claude.yml from workflow deploy list

Because scripts/deploy-standard-workflows.sh still includes claude.yml in DEPLOYABLE_WORKFLOWS (lines 38-46), deleting this template makes the default deployment path hit the missing-template branch at lines 138-140 for every target repo, and --workflow claude.yml can no longer do anything useful. Please remove or replace that deployable entry as part of retiring this template so the org workflow sync does not emit errors for an intentionally removed file.

Useful? React with 👍 / 👎.

github.event_name == 'check_run' && format('dev-lead-ci-relay-{0}', github.event.check_run.head_sha) ||
'dev-lead'
}}
cancel-in-progress: false
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve queued dev-lead events

With this workflow-level concurrency, every non-check_run trigger shares the literal dev-lead group, but cancel-in-progress: false alone does not create a full FIFO queue: GitHub's concurrency docs say the default queue is single, so a newer pending run cancels and replaces any existing pending run unless queue: max is set. In a busy repo, while one dev-lead run is active, a PR review submission followed by an @mention or issue label can drop the first pending automation event before it runs.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the deprecated claude.yml workflow template from the org standards catalog and updates the dev-lead.yml workflow templates to add a concurrency policy intended to limit agent runs to one active run per repo while allowing per-SHA check_run relay executions.

Changes:

  • Added a top-level concurrency block to dev-lead.yml workflow templates (standards + repo copy).
  • Removed the obsolete standards/workflows/claude.yml template from the standards directory.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File Description
standards/workflows/dev-lead.yml Adds concurrency grouping (static dev-lead, per-SHA for check_run).
standards/workflows/claude.yml Deletes the deprecated Claude workflow template from standards.
.github/workflows/dev-lead.yml Mirrors the same concurrency policy in the repo’s own dev-lead workflow stub.

Comment on lines +40 to +44
concurrency:
# One active run per repo; ci-relay (check_run) keeps an ephemeral per-SHA slot
# so it can fire immediately without blocking or being blocked by the dispatch queue.
group: >-
${{
@donpetry-bot
Copy link
Copy Markdown
Contributor

donpetry-bot commented May 30, 2026

Superseded by automated re-review at 77bd0c1b046c06306ca2f72fd12e3538d6dfc91d — 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

Automated review — NEEDS HUMAN REVIEW

Risk: MEDIUM
Reviewed commit: 77bd0c1b046c06306ca2f72fd12e3538d6dfc91d
Review mode: triage-approved (single reviewer)

Summary

Triage cleared this PR as low-risk, but a brief confirmation pass surfaced legitimate concerns the triage tier likely missed: the deletion of standards/workflows/claude.yml is not accompanied by the corresponding cleanup of references that point at it, and the PR silently bundles an unrelated concurrency change. Sending back for human review (or for the author to address) rather than auto-approving.

Linked issue analysis

No linked issues. The PR description references PR #301 as the migration that retired claude.yml in favor of dev-lead.yml, and states "All org repos have migrated to dev-lead.yml." That migration claim was not verified, but is plausible given the historical context already documented in standards/ci-standards.md.

Findings

1. Incomplete cleanup — dangling references to standards/workflows/claude.yml (MEDIUM)

The PR description says it removes the obsolete template "from the org-level standards directory and workflow template catalog," but the following references remain and will become stale or actively broken:

  • scripts/deploy-standard-workflows.sh line 42claude.yml is still in DEPLOYABLE_WORKFLOWS. With the template gone, the default deploy path will hit the [[ ! -f "$template" ]] branch at lines 138–140 (err "No template at $template — skipping $workflow for $repo") for every target repo, polluting deploy output and signaling an incomplete retirement. --workflow claude.yml becomes a no-op error path. Already flagged by the codex bot review comment.
  • AGENTS.md line 19 — still lists claude.yml as one of the copy-paste-ready workflow templates available under standards/workflows/. After this PR merges, that link will 404 on main.
  • standards/ci-standards.md line 309 — explicitly states "The template at standards/workflows/claude.yml is preserved for historical reference." This will directly contradict reality after the merge, and the link itself will be broken. Lines 301–358 and the §Migration block (1114+) also still reference the now-deleted file in ways that should be reviewed for consistency. Flagged by the Copilot review comment.
  • scripts/compliance-audit.sh — defines check_claude_workflow_checkout and related logic around claude.yml (lines 634–668). The actual call site at line 1581 is already commented out (# removed: claude.yml retired 2026-05), so the dead code is harmless, but worth cleaning up while removing the template.

2. PR scope drift (LOW)

The PR title and description describe only the claude.yml deletion, but the diff also includes a concurrency-block addition to both .github/workflows/dev-lead.yml and standards/workflows/dev-lead.yml (commit 7d57c04 from 2026-05-18, "feat(concurrency): add per-repo serialized concurrency to dev-lead stubs"). The concurrency change appears to be intentional and well-reasoned, but bundling unrelated changes makes the PR harder to revert independently if one of them turns out to be wrong. Recommend either splitting or updating the PR description to call this out.

3. Concurrency design — possible queue-drop under load (LOW)

The codex bot raised a valid concern: with group: 'dev-lead' (shared) and cancel-in-progress: false, GitHub's default queue: single policy means a newer pending run can displace an older pending run while one is active. In a busy repo this could silently drop queued dev-lead events (e.g., a review submission followed by an @mention). This is a behavior worth confirming matches the author's intent before adopting org-wide — the policy was lifted from .github-private per the commit message, so it may already be intentional.

Note on the gemini-code-assist comment: the suggestion to scope the concurrency group per PR/issue runs counter to the commit's explicit intent ("at most one dev-lead dispatch run executes per repo at a time"). That feedback can be dismissed.

CI status

All required checks green: CodeQL, AgentShield, Lint, ShellCheck, Agent Security Scan, Secret scan (gitleaks), SonarCloud, Dependency audit detect step. CodeRabbit was rate-limited so it did not analyze this PR. Mergeable but BEHIND main — will need a rebase or update-branch before merge.


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

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
Copy link
Copy Markdown
Contributor

donpetry-bot commented May 30, 2026

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

Review — fix requested (cycle 2/3)

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

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: MEDIUM
Reviewed commit: 77bd0c1b046c06306ca2f72fd12e3538d6dfc91d
Review mode: triage-approved (single reviewer)

Summary

Triage cleared this PR as low-risk, but a confirmation pass shows the deletion of standards/workflows/claude.yml is incomplete: several references in the same repo still point at the file and will be stale or broken after merge. The prior cycle's review on this same SHA already identified these issues and they remain unaddressed. Re-escalating rather than auto-approving.

Linked issue analysis

No linked issues. The PR description references PR #301 as the migration that retired claude.yml in favor of dev-lead.yml, and asserts all org repos have migrated. The migration claim is plausible given the historical context in standards/ci-standards.md, but was not independently verified.

Findings

The findings from the prior cycle's review still stand on this unchanged SHA. Reconfirmed against the current branch:

1. Incomplete cleanup — dangling references to standards/workflows/claude.yml (MEDIUM, unresolved)

  • scripts/deploy-standard-workflows.sh:42claude.yml is still in DEPLOYABLE_WORKFLOWS. After this PR, the default deploy path hits the missing-template branch at lines 138–140 (err "No template at $template — skipping $workflow for $repo") for every target repo.
  • AGENTS.md:19 — still lists claude.yml as a copy-paste-ready workflow template under standards/workflows/. The link will 404 on main.
  • standards/ci-standards.md:309 — states "The template at standards/workflows/claude.yml is preserved for historical reference." This will directly contradict reality after merge, and the link will be broken. Lines 301–358 and §Migration (1114+) reference the deleted file in ways that should be reviewed for consistency.
  • scripts/compliance-audit.sh:634-668check_claude_workflow_checkout and its helpers remain defined; the call site at line 1581 is already commented out (# removed: claude.yml retired 2026-05), so this is dead code rather than broken, but worth cleaning up in the same PR.

2. PR scope drift (LOW, unresolved)

The title and description describe only the claude.yml deletion, but the diff also bundles the concurrency-block addition to both .github/workflows/dev-lead.yml and standards/workflows/dev-lead.yml (commit 7d57c04). The concurrency change is reasonable on its own, but bundling unrelated changes complicates revertability. Either split or update the PR description.

3. Concurrency design — possible queue-drop under load (LOW, design question)

With group: 'dev-lead' (shared, repo-wide) and cancel-in-progress: false, GitHub's default queue: single policy lets a newer pending run displace an older pending run while one is active. In a busy repo this could silently drop queued dev-lead events. The commit message says this matches the policy already in .github-private, so it may be intentional — worth a quick confirmation before adopting org-wide.

On the gemini-code-assist comment: the suggestion to scope the concurrency group per PR/issue runs counter to the commit's explicit intent ("at most one dev-lead dispatch run executes per repo at a time"). That feedback can be dismissed.

CI status

All required checks green: CodeQL, AgentShield, Lint, ShellCheck, Agent Security Scan, Secret scan (gitleaks), SonarCloud, Dependency audit. CodeRabbit was rate-limited — rebase or update-branch needed before merge.


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

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.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 87f9c4c80f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@@ -1,68 +0,0 @@
# ─────────────────────────────────────────────────────────────────────────────
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve the documented claude template path

Deleting this template leaves several standards/remediation paths pointing at a file that no longer exists: standards/ci-standards.md:310 says standards/workflows/claude.yml is preserved for historical reference, standards/agent-standards.md:30 says immutable workflow files are adopted verbatim from standards/workflows/, and scripts/compliance-audit.sh:1258 still advertises claude.yml as an available template. Anyone following the standards or generated audit remediation now gets a 404/missing file for this documented path, so either keep an archived copy or update those catalogs/references as part of the removal.

Useful? React with 👍 / 👎.

@sonarqubecloud
Copy link
Copy Markdown

@donpetry-bot
Copy link
Copy Markdown
Contributor

Review — fix requested (cycle 3/3)

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

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: MEDIUM
Reviewed commit: ae261d947cd67f405d2f5d8c45c3b39b186970b6
Review mode: triage-approved (single reviewer, cycle 3/3)

Summary

Triage cleared this PR as low-risk, but a confirmation pass shows the deletion of standards/workflows/claude.yml is still an incomplete cleanup: several in-repo references will be stale or actively broken after merge. The two prior review cycles flagged the same finding, and the new commits on this branch since the prior review SHA (77bd0c1b…) are only merges from main — none of the dangling references have been touched. At the final cycle, escalating rather than auto-approving.

Linked issue analysis

No linked issues. The PR description references PR #301 as the migration that retired claude.yml in favor of dev-lead.yml. That migration claim is plausible given the historical context already captured in standards/ci-standards.md, but it isn't independently re-verified here.

Findings

1. Incomplete cleanup — dangling references to standards/workflows/claude.yml (MEDIUM, unresolved across 3 cycles)

Verified against the current head (ae261d94) of chore/remove-deprecated-claude-yml:

  • scripts/deploy-standard-workflows.sh:43claude.yml is still listed in DEPLOYABLE_WORKFLOWS. After this PR merges, the default deploy path will hit the missing-template branch (err "No template at $template — skipping $workflow for $repo") for every target repo, polluting deploy output and signaling an incomplete retirement. This is the most consequential dangling reference — it produces runtime errors, not just stale docs.
  • AGENTS.md:19 — still lists claude.yml as a copy-paste-ready workflow template under standards/workflows/. The implied link will 404 on main after merge.
  • standards/ci-standards.md:309–310 — explicitly states "The template at standards/workflows/claude.yml is preserved for historical reference." This will directly contradict reality after merge, and the link will be broken. Lines 302–359 and the §Migration block (1200+) also still reference the deleted file in ways worth reviewing for consistency.
  • scripts/compliance-audit.sh:1258 — error message still advertises claude.yml as one of the available templates. (The call site for check_claude_workflow_checkout at line 1754 is already commented out, so the surrounding helper at lines 637–671 is dead code rather than broken — still worth cleaning up alongside the deletion.)

2. PR scope drift — RESOLVED at this SHA

The prior cycles noted that the concurrency change to dev-lead.yml was bundled in. That change has since landed on main via #322 and is no longer part of this PR's diff (the only diff vs. base is now the single-file deletion of standards/workflows/claude.yml, −68/+0). No action needed.

3. Concurrency design (LOW) — RESOLVED here

No longer in scope for this PR (see #2). Any follow-up on the group: 'dev-lead' / cancel-in-progress: false policy belongs against #322 or a follow-up PR, not this one.

CI status

All required checks green or skipped: CodeQL, AgentShield, Lint, ShellCheck, Agent Security Scan, Secret scan (gitleaks), SonarCloud (Quality Gate passed, 0 new issues), Dependency audit detect step, pr-auto-review. mergeable: MERGEABLE, mergeStateStatus: BLOCKED only on review-required.


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

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
Copy link
Copy Markdown
Contributor

Automated review — human attention needed

This PR has been through 3 automated review cycles (cap: 3) without converging on an approval-and-merge state. Further automated review has been paused to avoid infinite loops.

Please take a look manually, or close this PR if it's no longer needed. Once a human review resolves the situation, remove the needs-human-review label and the cascade can be re-engaged on the next push.

Posted by the donpetry-bot PR-review cascade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants