GitHub's hosted runners are thrown away after each job. Your own runner is not, and GitHub's own guidance says it should almost never serve a public repository, because any pull request can run code on it.
Some Rust crates fetch a prebuilt native library while they compile. The build works for months from a local cache, then a clean machine meets a refusing download host. Cargo's offline mode does not cover that download.
Thomas Dohmke's Entire launches a Git-compatible forge with Trails, review agents, merge Gates, GitHub mirroring and two MIT-licensed memory CLI plugins.
In preview for GitHub Enterprise Cloud, it blocks malware, risky versions, new install scripts and too-fresh npm packages before agents or CI install them.
After five years at 0.x, Dagger 1.0 is in beta with official modules, per-test results, dev shells and GitHub checks. Expect CLI and config breaking changes.
Cargo's default job count is the number of logical CPUs. On a machine with many cores and several builds at once, memory becomes the limit long before CPU. Three ways to set the job count, and how to pick one.
Turn promptfoo assertions into a required GitHub check: deterministic tests, the action's failure rules, branch protection, and the path-filter trap that leaves checks pending.
A shallow CI checkout can build the current tree while hiding the ancestor a change detector needs. Diagnose missing history, deepen deliberately, and fetch the right refs.
A pipeline, a log tee or a local variable can turn a failed command into exit status 0. Patterns that hide failure from CI and AI agents, and how to make the status tell the truth.