FP606 · missing-local-target
A local `uses: ./...` or `uses: $/...` points to a workflow or action that does not exist where GitHub looks for it, or is written in a form GitHub rejects.
| Code | Name | Category | Default severity |
|---|---|---|---|
FP606 | missing-local-target | Graph structure | 🔴 error |
Why it matters
The job or step fails as soon as it is reached, usually after a rename or move. A step’s ./path is relative to the runner’s workspace: flowpact maps it through the actions/checkout steps before it (for a composite action, each caller’s) and reports it when it lands in this repository but is missing, or when no checkout puts this repository where it points. Paths it cannot read are FP610.
How to fix
Fix the path or restore the missing file. A step’s ./path includes the path: this repository is checked out to, and needs a checkout that puts it there; $/path and a job’s ./path are relative to the repository root whatever the checkout, and $/ takes no @ref (it always runs the running commit).
Example
- uses: actions/checkout@v5
with:
path: src/app
- uses: ./src/app/.github/actions/biuldConfigure
Change the severity (or turn the rule off) in .github/flowpact/flowpact.config.yml, by code or by name:
rules:
FP606: off
# or: missing-local-target: errorExplain it in the terminal:
flowpact explain FP606