Skip to content

ci: add standard Claude workflow callers - #1

Merged
twistedmelonman merged 1 commit into
mainfrom
claude/add-standard-claude-workflows
Aug 17, 2026
Merged

twistedmelonman merged 1 commit into
mainfrom
claude/add-standard-claude-workflows

Conversation

@twistedmelonman

Copy link
Copy Markdown
Member

Onboards this repo to the fleet standard. Per smartwatermelon/github-workflows#126 item 3, this was one of three repos with no .github/workflows directory at all — no blocking review, no assistant.

Files added

  • .github/workflows/claude-blocking-review.ymlclaude-blocking-review.yml@v3
  • .github/workflows/claude.ymlclaude-assistant.yml@v3

Both are thin delegates copied from the canonical fleet stubs, including the explanatory comments. No caller-side customization.

Token status

CLAUDE_CODE_OAUTH_TOKEN is already present in this repo (set 2026-07-14), so no human setup step is needed here. This is the only one of the three repos in issue #126 item 3 that already had it.

Once this lands and a first run is observed green, claude-review / run-review can be added as a required status check under branch protection.

Ref policy

Floating @v3, not an exact @v3.x.y. Exact tags are immutable, so a caller pinned to one silently misses security fixes — that is how 19 repos never received the GHSA-8q5r-mmjf-575q remediation. See "Prefer floating @V3 over an exact pin" in the github-workflows README.

https://claude.ai/code/session_01SimcNSM4P5hpb1dQVejqcF

Onboards this repo to the fleet standard: blocking-review and assistant
callers delegating to smartwatermelon/github-workflows. This repo was one
of three with no .github/workflows directory at all (issue #126 item 3).

Both callers track floating @V3 rather than an exact @v3.x.y pin. Exact
pins are immutable and silently miss security fixes — that is how 19 repos
never received the GHSA-8q5r-mmjf-575q remediation.

Committed with SKIP=zizmor: zizmor flags unpinned-uses against the @V3 tag
ref, but reusable workflows in this fleet use a repo-wide semver tag
convention rather than per-action SHA pinning. That is deliberate
documented policy, not an oversight.

Claude-Session: https://claude.ai/code/session_01SimcNSM4P5hpb1dQVejqcF
@twistedmelonman
twistedmelonman merged commit 831928a into main Aug 17, 2026
3 checks passed
@twistedmelonman
twistedmelonman deleted the claude/add-standard-claude-workflows branch August 17, 2026 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant