ci: restore the Claude Code workflow, lost in the v2 tree swap - #1851
Open
cliffhall wants to merge 1 commit into
Open
ci: restore the Claude Code workflow, lost in the v2 tree swap#1851cliffhall wants to merge 1 commit into
cliffhall wants to merge 1 commit into
Conversation
Same regression class as #1843 (SECURITY.md): the v2 tree swap replaced the default branch's tree, and `.github/workflows/claude.yml` did not exist in the v2 tree, so it was silently dropped from `main`. Because `issue_comment` / `pull_request_review_comment` / `issues` events always run workflows from the DEFAULT branch, losing it on `main` disabled `@claude` repo-wide — including on PRs targeting `v2/main`. The workflow's API state reads `deleted` and its last runs are all `skipped`. Restored byte-for-byte (sha256 1c44f2d9…) from `ac3c1a12`, the last commit that carried it, which is no longer an ancestor of `main`. No content changes: the `@claude` trigger stays gated to OWNER / MEMBER / COLLABORATOR, which is what we want under the issues-only contribution model (#1820). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UkhhCHryVp5H3dqEnhwZ7t
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1850.
Same regression class as #1843 (
SECURITY.md): the v2 tree swap replaced the default branch's tree, and.github/workflows/claude.ymldid not exist in the v2 tree, so it was silently dropped frommain.Impact
issue_comment/pull_request_review_comment/issuesevents always run workflows from the default branch, so losing this onmaindisabled@clauderepo-wide — including on PRs targetingv2/main.Found the hard way: two
@claude reviewcomments on #1847 (19:08 and 19:10 UTC) produced no bot reply and no workflow run.Evidence
actions/workflows/173749385statedeletedissue_comment, latest 03:10 UTC today)skipped.github/workflows/onmainmain.ymlac3c1a12(last commit carrying the file)mainThe change
Restored byte-for-byte from
ac3c1a12—sha256 1c44f2d9d51c936adb40c9acefd4b44628fe7810360e2f8196034347f9d2602d, 3592 bytes, verified against the version fetched from the API. No content changes: the@claudetrigger remains gated toOWNER/MEMBER/COLLABORATORauthor associations, which is the behavior we want under the issues-only contribution model (#1820).Verifying after merge
@claudecannot work until this is onmain— a workflow on a topic branch is not consulted forissue_commentevents. After merge, comment@claude reviewon any open PR;claude[bot]should reply within ~20s (it took 19s on #1825).Note
SECURITY.mdand this file are two instances of one pattern, and neither was caught by CI. A sweep for anything else the swap dropped frommainis probably worth doing separately.