What is wrong
For an action declaring no inputs, the generated usage block still emits a with: key with no entries beneath it:
- uses: acme/t@v1.2.3
with:
Where it was observed
The usage section, src/sections/update-usage.ts. The with: line is emitted unconditionally, before the input loop.
Evidence
Reproduced against the built binary with an action declaring no inputs: block. The output above is the complete generated usage section.
Two things I checked at the same time, which did not reproduce: the run exited 0, the text after the markers was preserved, and an existing inputs section body was left intact. The README truncation described in #195 does not occur on this version — that part appears to have been fixed since.
What remains is the objection the reporter of #195 actually raised: "I would expect this to be generated, and absent a 'with:' stanza as there are 0 inputs. Use case is for custom composite actions which require no input."
Impact
Zero-input actions are an ordinary shape, particularly for composite actions. A user copying the snippet gets a dangling with: they have to know to delete.
What is wrong
For an action declaring no inputs, the generated usage block still emits a
with:key with no entries beneath it:Where it was observed
The
usagesection,src/sections/update-usage.ts. Thewith:line is emitted unconditionally, before the input loop.Evidence
Reproduced against the built binary with an action declaring no
inputs:block. The output above is the complete generated usage section.Two things I checked at the same time, which did not reproduce: the run exited 0, the text after the markers was preserved, and an existing
inputssection body was left intact. The README truncation described in #195 does not occur on this version — that part appears to have been fixed since.What remains is the objection the reporter of #195 actually raised: "I would expect this to be generated, and absent a 'with:' stanza as there are 0 inputs. Use case is for custom composite actions which require no input."
Impact
Zero-input actions are an ordinary shape, particularly for composite actions. A user copying the snippet gets a dangling
with:they have to know to delete.