Repository navigation
ci-parity: lint GitHub Actions workflows so CI calls your Taskfile tasks #3086
jimmykurian
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've released 1.0 of ci-parity, a linter for the gap between a Taskfile and the CI that's meant to run it.
It reads your workflows and your Taskfile statically (it never runs
task) and reports:pnpm test,go test ./...) instead of the task, with "already available astask test" when a task runs exactly that command;taskcalls to tasks that don't exist, with the closest name;internal: truetasks.It follows
includes(namespaces, aliases,flatten,dir:), thego tool …/cmd/taskform, and task's flags. And it keeps a per-workflow baseline that only shrinks, so an existing repository can adopt it without fixing everything at once.ci-parity fixrewrites the steps that are safe to change.Before 1.0 I ran it on 10 public repositories, go-task/task among them, and fixed every false positive it found. The results are on the field trial page. It also reads make, just and mise, but Taskfile is where it started.
Docs: https://ci-parity.is-a.dev/ · Code: https://github.com/jimmykurian/ci-parity
Feedback welcome, especially Taskfile features it reads wrong.
All reactions