ci/check-workflow
CI runs the check
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | any |
| Scope | root |
| Kind | outcome |
| Source | library v0.7.0 |
| Selected by | fleetlint-recommended@v0.7.0 |
Requirement
A CI workflow or pipeline that runs on pushes or pull requests (GitLab: branch or merge request pipelines) runs the same check the hooks run: make check, just check, task check, npm run check, ./gradlew check and the like, a check script (./scripts/check.sh), or the same inside the dev container (devcontainers/ci runCmd). check-fast does not count. A repository whose check has another name adds it with accept:.
Why
CI is the record that main was green; it must run the same gate as local, not a different subset.
Fix
Add a check workflow for the stack; fleetlint fix --apply writes the template for the repository’s task runner and container setting.
Agent instruction: Add .github/workflows/check.yml from the stack template (toolchain setup, shared tools, the task runner’s check), or a GitLab job running the task runner’s check.
fleetlint fix can apply this rule’s fix automatically (1 action(s)).
A finding of this rule points at .github/workflows/check.yml.
Sources
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, CI-Tests)
- https://fleetlint.org/baseline/#continuous-integration (convention)
Generated by fleetlint docs from catalog v0.7.0.