Rules
FP104 · unused-input
An input is declared but never read anywhere in the workflow or action.
| Code | Name | Category | Default severity |
|---|---|---|---|
FP104 | unused-input | Inputs | 🟡 warning |
Why it matters
Dead inputs accumulate in large interfaces: callers keep computing and passing values that go nowhere, and readers assume a knob works when it does not.
How to fix
Remove the input (and the callers’ bindings), or wire it to where it was meant to be used.
Example
on:
workflow_call:
inputs:
legacy-flag: { type: boolean } # never referencedConfigure
Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:
rules:
FP104: off
# or: unused-input: errorExplain it in the terminal:
flowpact explain FP104