prompt_file supported by claude-code-action@v1?

[ring-pete]

Hello,
I have a workflow where we want to invoke a pretty complicated prompt triggered by github actions. The documentation I've found for the claude-code-action github action references the prompt argument, but most examples have the prompt inline in the action YAML config.

I do find reference to a config option prompt_file in claude-code-base-action@beta here:
https://github.com/anthropics/claude-code-base-action

Referring to an external file for the prompt to execute is preferred in our specific use-case.

My question is twofold:

1. Is claude-code-base-action supported? Is @beta the correct tag if it is?
2. does claude-code-action have the ability to refer to a prompt file for execution?

[sueun-dev]

two answers:

1. claude-code-base-action is real and not archived, it's an automated mirror of the base-action folder inside claude-code-action (its README points issues/PRs back to the main repo). @beta does resolve to a real tag, but it moves, so pinning a semver like @v0.0.63 is safer.

2. claude-code-action@v1 itself doesn't take a prompt file. I parsed its action.yml: 39 inputs, prompt is there but prompt_file isn't. that input only lives on base-action ("Path to a file containing the prompt", mutually exclusive with prompt). so either use base-action directly, or on v1 read the file in a prior step and pass it in:

- id: p
  run: |
    { echo 'body<<EOF'; cat my_prompt.md; echo EOF; } >> "$GITHUB_OUTPUT"
- uses: anthropics/claude-code-action@v1
  with:
    prompt: ${{ steps.p.outputs.body }}