Skip to content

Add claude pr automations#89

Open
rohita5l wants to merge 6 commits into
mainfrom
add-claude-pr-automations
Open

Add claude pr automations#89
rohita5l wants to merge 6 commits into
mainfrom
add-claude-pr-automations

Conversation

@rohita5l
Copy link
Copy Markdown
Collaborator

No description provided.

rohita5l and others added 6 commits May 26, 2026 13:38
claude-mention.yml triggers anthropics/claude-code-action when "@claude"
appears in an issue, PR comment, review, or review comment. Useful for
ad-hoc requests ("@claude please fix the flake in test_X").

claude-review.yml runs the action on PR open and posts a single review
focused on correctness, conventions, security, and test coverage. Limited
to [opened] (not synchronize) to keep cost and noise low; flip to add
synchronize if you want re-review on every push.

Both pin actions/checkout to v4.2.2 (same SHA as ci.yml) and pin
claude-code-action to the v1 commit. Requires ANTHROPIC_API_KEY in repo
secrets.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Adds job-level env: blocks to both Claude workflows that forward
ANTHROPIC_BASE_URL, ANTHROPIC_CUSTOM_HEADERS, and the three
ANTHROPIC_DEFAULT_*_MODEL overrides from repo secrets to the action.

The action is a composite action and reads these via env.X, so they
must be set at the job (or workflow) level rather than on the
uses: step. Unset secrets expand to empty strings, which the action
treats as "no override" — so you only create the secrets you actually
want to apply.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Custom headers (just the coding-agent-mode flag) and the three model
ID overrides are config, not credentials, so hardcode them in the
workflow files. Leaves ANTHROPIC_API_KEY and ANTHROPIC_BASE_URL as the
only repo secrets needed.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Databricks AI Gateway only accepts Authorization: Bearer, so the auth
header has to live inside ANTHROPIC_CUSTOM_HEADERS rather than going
through ANTHROPIC_API_KEY (which the CLI sends as x-api-key). That
makes CUSTOM_HEADERS sensitive and it has to come from secrets.

ANTHROPIC_API_KEY stays referenced because the action requires the
input — the value is ignored by the gateway, so a placeholder works.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Only the Authorization: Bearer line carries the PAT, so that's the
sensitive part worth hiding in a secret. The x-databricks-use-coding-
agent-mode header is just a feature flag and lives in the workflow YAML
where it can be sanity-checked at a glance.

The two are concatenated into ANTHROPIC_CUSTOM_HEADERS via a YAML block
scalar; the Claude CLI splits on newlines so both headers get sent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Single secret holds the raw PAT; the workflow prefixes "Authorization:
Bearer " when assembling ANTHROPIC_CUSTOM_HEADERS. Same PAT also flows
to the action's anthropic_api_key input (gateway ignores the resulting
x-api-key header, no harm). Removes the need for a separate
ANTHROPIC_AUTH_HEADER secret.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@rohita5l rohita5l requested a review from AarushiShah-db as a code owner May 26, 2026 18:03
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.

2 participants