Flaky task detection
Local and free: the same key failing after it passed is called flaky.
A task is flaky when its exact cache key failed after it had passed, or when it needed a retry. Its row says so, from the local run history alone, and vx info keeps the standing list.
Failing on new inputs is a break, not a flake, and carries no note.
More in CI
Run only what a change reaches
--affected follows task edges from the change, and nothing else runs.
vx lock
CI runs exactly the config you reviewed.
Results on GitHub
Every run on GitHub Actions writes a job summary and a check.
Results on the pull request
A check run on the commit carries the run summary, failures first.
Cache scope from the branch
On Actions, main writes trusted cache entries and a pull request writes only its own.