Skip to content

Commit 2f871a0

Browse files
authored
fix(action.yaml): drop github.actor example from idempotency-key description (#33)
GitHub Actions evaluates `${{ }}` expressions in `action.yaml` at action-load time, including inside `description` strings, so the literal `${{ github.actor }}` in the `idempotency-key` description fails the action loader with `Unrecognized named-value: 'github'` for every consumer of `main`. Rewrites the example sentence in plain prose so no `${{ }}` literal survives. The action-load failure is only observable via GitHub Actions' own loader, so the correctness check is reviewer eyeball on `action.yaml` line 62. Failing consumer run: https://github.com/coder/coder/actions/runs/26046090719 🤖 Authored by Coder Agents.
1 parent 4a30625 commit 2f871a0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

action.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ inputs:
5959
default: "600"
6060

6161
idempotency-key:
62-
description: "Optional sharding key to narrow the default reuse scope. By default the action reuses the most recent non-archived chat scoped to `gh-target` and the workflow name (when `GITHUB_WORKFLOW` is set). All chats are owned by the `coder-token` holder, so the scope does not include a per-actor component. Set this to maintain multiple parallel chats on the same target/workflow (for example, one per matrix dimension). Pass `${{ github.actor }}` here if you want per-actor separation."
62+
description: "Optional sharding key to narrow the default reuse scope. By default the action reuses the most recent non-archived chat scoped to `gh-target` and the workflow name (when `GITHUB_WORKFLOW` is set). All chats are owned by the `coder-token` holder, so the scope does not include a per-actor component. Set this to maintain multiple parallel chats on the same target/workflow (for example, one per matrix dimension). Pass the github.actor workflow expression to maintain one chat per triggering user."
6363
required: false
6464

6565
force-new-chat:

0 commit comments

Comments
 (0)