Commit e9b53eb
committed
fix: stop GitHub from evaluating example expressions in action.yml
GitHub's runner evaluates `${{ ... }}` tokens that appear anywhere in
`action.yml` — including inside `description:` blocks — when it loads
the action manifest. Embedding `${{ github.sha }}` and
`${{ secrets.OPENAI_API_KEY }}` literally as documentation examples
caused every workflow that referenced this action to fail at load time
with `Unrecognized named-value: 'github'` and `'secrets'`.
Replace the four offending example tokens with placeholders that don't
resemble Actions expressions:
- `tags` example: `commit: ${{ github.sha }}` → `commit: <commit-sha>`
- `branch` description: ``Defaults to `${{ github.ref_name }}`.`` →
``Defaults to the `GITHUB_REF_NAME` environment variable.``
- `commit-sha` description: same treatment with `GITHUB_SHA`.
- `secrets` example: `KEY=${{ secrets.* }}` → `KEY=<placeholder>`.
Real workflow examples in README.md and examples/ are unaffected
because expressions inside workflow files are evaluated normally.1 parent f84b3ab commit e9b53eb
1 file changed
Lines changed: 5 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
50 | | - | |
| 50 | + | |
51 | 51 | | |
52 | 52 | | |
53 | 53 | | |
| |||
74 | 74 | | |
75 | 75 | | |
76 | 76 | | |
77 | | - | |
| 77 | + | |
78 | 78 | | |
79 | 79 | | |
80 | | - | |
| 80 | + | |
81 | 81 | | |
82 | 82 | | |
83 | 83 | | |
| |||
93 | 93 | | |
94 | 94 | | |
95 | 95 | | |
96 | | - | |
97 | | - | |
| 96 | + | |
| 97 | + | |
98 | 98 | | |
99 | 99 | | |
100 | 100 | | |
| |||
0 commit comments