Topic · 11 stories
11 stories tagged ci on AI Tamer, newest first.
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.
Switch a Rust test suite to cargo-nextest so each test runs in its own process, flaky tests can retry, and slow or hung tests are flagged and stopped.
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.
Use npm ci in CI so builds install the committed dependency tree, and learn why it errors when package.json and package-lock.json disagree.
Send breakpoint() calls to pdb, another debugger, a custom hook, or nowhere, by setting one environment variable instead of editing code.
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 concurrency group can cancel a waiting GitHub Actions run when a newer one arrives. Here is how to keep a queue when each run matters.
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.
