Skip to content

NAS-142108 / 27.0.0-BETA.1 / Feat/shared check-member & prepare action - #2

Merged
AlexKarpov98 merged 11 commits into
masterfrom
feat/shared-claude-review
Aug 10, 2026
Merged

NAS-142108 / 27.0.0-BETA.1 / Feat/shared check-member & prepare action#2
AlexKarpov98 merged 11 commits into
masterfrom
feat/shared-claude-review

Conversation

@AlexKarpov98

Copy link
Copy Markdown
Contributor

No description provided.

AlexKarpov98 and others added 5 commits August 7, 2026 11:48
A reusable call reports as "<caller job id> / <this job name>", so consumers put
that whole string in branch protection. Renaming the job here stops their required
check reporting, with nothing in their repo to explain it.

The usage example still showed @v1. Consumers track master — the tag was retired
rather than kept moving, since a v1 re-pointed at every merge is master with a
force-push in front of it.
Collapses the near-identical claude.yml carried by all three consumers.
They had drifted: claude-code-action v1.0.7 / v1.0.134 / v1.0.182, models
claude-opus-4-8 / claude-opus-5 / action default, and a write-access gate
present in two of the three.

Notes on two design choices:

- The action version is hardcoded rather than an input. `uses:` does not
  evaluate expressions, and a configurable version is how the three
  repos drifted in the first place. Bump here, re-tag, all callers move.
- The API key is an explicit named secret rather than `secrets: inherit`,
  because the repos name it differently (CLAUDE_API_KEY vs CLAUDE_TOKEN).

The member gate is inlined as a job instead of a second reusable
workflow: relative `uses:` paths inside a reusable workflow resolve
against the caller's repository, which is a footgun with no upside here.
webui's check-ux-team.yml and ui-components' check-member.yml turned out
to be byte-identical apart from `name:` — neither checked a team, both
checked repo write access — so the gate needs no parameterisation.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MMo51bM6QV14CK3Kgyp3DQ
@AlexKarpov98 AlexKarpov98 self-assigned this Aug 7, 2026
@AlexKarpov98
AlexKarpov98 requested a review from william-gr August 7, 2026 15:29
@bugclerk bugclerk changed the title Feat/shared claude review & check-member & prepare action NAS-142108 / 27.0.0-BETA.1 / Feat/shared claude review & check-member & prepare action Aug 7, 2026
@bugclerk

bugclerk commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

@william-gr william-gr left a comment

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.

Lets leave claude out for now please. me and Aaron are working on changes

@AlexKarpov98 AlexKarpov98 changed the title NAS-142108 / 27.0.0-BETA.1 / Feat/shared claude review & check-member & prepare action NAS-142108 / 27.0.0-BETA.1 / Feat/shared check-member & prepare action Aug 10, 2026
@AlexKarpov98
AlexKarpov98 merged commit 117206a into master Aug 10, 2026
3 checks passed
@AlexKarpov98
AlexKarpov98 deleted the feat/shared-claude-review branch August 10, 2026 12:50
@bugclerk

Copy link
Copy Markdown
Contributor

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.

@iXsystems iXsystems locked as resolved and limited conversation to collaborators Aug 10, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants