Automating SSL Renewals in GitHub Actions with acme.sh
Automating SSL Renewals in GitHub Actions with acme.sh When our infrastructure team inherited a legacy deployment pipeline that required manual SSL…
Latest News
⚑ Report a ProblemTech news from the best sources
All topics
AI
Gear
News
Tech
agents
ai
api
architecture
automation
beginners
career
database
devchallenge
devops
discuss
javascript
llm
machinelearning
mcp
opensource
performance
productivity
programming
python
security
showdev
testing
tutorial
typescript
webdev
The build went green because it stopped checking
A teammate deleted a test file on a Friday. Not on purpose. The suite still passed. The pipeline still went green. Nobody noticed for three weeks. H…
Runbook Rot: Three Fingerprints of Stale CI Docs and the Check That Catches Each
A runbook is the only document in your repo that gets read at 3 a.m., under adrenaline, by someone who trusts it. When the code is stale you get a b…
The Agent Wrote a Test That Mocks the Function Under Test
The test file passed. The function it was supposed to cover was broken. The mock was the giveaway. CI went green. Coverage on the new module jumped…
When the agent calls the failing test "pre-existing" and merges anyway
The PR comes in. CI is red. The agent's summary says: "Two tests failed — test_checkout_total and test_inventory_lock . Both were already failing on…
Your Agent Added a Retry Loop. It Hid the Bug Instead of Fixing It.
You hand the agent a failing test: an upload that flakes about one run in ten. It comes back green. You open the diff and find a for (let i = 0; i &…
Your Agent Says Tests Pass. On Your Laptop. Not on CI.
The agent ran the test command, watched the green checkmark, and said done. You opened the PR. Twenty minutes later CI was red. The agent looked at…
Tests are the only fixed point left when the implementation is disposable
Originally published at https://aicoding-guide.com . The more disposable the implementation becomes, the more the spec moves into the tests. That is…
A Command That Matched Zero Files Still Exits 0: How to Catch Silent CI Failures
A Command That Matched Zero Files Still Exits 0: How to Catch Silent CI Failures Every engineer has felt the cold dread of pushing a critical fix, w…
AI code review in CI when tests pass but design fails
My coding agent can write a feature, add tests, and hand me a green build. It can also put the right behavior in the wrong place. The application wo…
We Deleted Our CI. The Machine Ships Anyway.
Provenance: this site is run by an AI agent under a human owner's approvals. This story comes from today's deploy ledger. Full archive at mrsaynothi…
Growing Pains with Five Repositories: Gitlinks and Dual CI
Usually, infrastructure stories start with the words: "Our project got too big, and we decided to split it into parts." But with us, everything was…
A Scorecard for Agent Diffs: Fixture Digests, Seed Replay, and Failure Signatures
A green unit-test job is not evidence that an agent patch is safe to merge. Agents can keep pytest quiet by rewriting golden files, dropping hard ge…
Linear cut CI runner-time in half while tests quadrupled. The review gate can't do that trick.
Linear put up a really good post about reworking their CI because AI coding agents had turned it into the bottleneck. The numbers are worth reading…
Breaking the CI Bottleneck: Architecting Pipelines for the AI Code Era
Originally published on tamiz.pro . The introduction of Large Language Model (LLM)-assisted coding tools has fundamentally altered the velocity of s…
Blacksmith's GitHub Actions runners finished the same job 3 to 4 times faster than GitHub hosted Actions, across 10 trials
Disclosure: I have no affiliation with Blacksmith. Nobody asked me to write this and nobody paid for it. I installed their GitHub App like anyone el…
WEEKEND HOMEWORK — Restaurant Company CI
Goal: Practice Trivy, understand vulnerabilities and dependency trees, and create a GitHub Actions pipeline with 3 independent parallel jobs: Lint,…
Markdown woes: Looks right, is wrong
Your Markdown can be perfectly rendered and completely wrong Markdown has an unfair advantage: it looks trustworthy. A table lines up, the headings…
Green Coverage, Broken Inverse: A Round-Trip Gate for Agent Patches
Agent patches can raise line coverage while destroying invertibility. A merge bar that only asks “did pytest exit 0?” will accept a codec that no lo…
Four Identical Red Runs: One Was Our Watchdog Working, Three Were Its Corpse
A cron in one of our repositories stopped firing on 21 June and nobody noticed for ten weeks. Its only job was to rebuild this site each morning so…
The Env Catalog Is a Repository Artifact
59 variables, generated not written - and drift fails the build. 👋 I'm Anton - a software engineer working mostly in PHP/Symfony and Go, currently c…
Merge Agent Patches Only When Two Test-World Receipts Match
A green CI job is not proof that an agent patch preserved the test world. Fixtures can be rewritten to match new output. Property suites can shrink…
Treat Merge as Promotion: Four Stages Between Local Green and main
A green check is a local fact. Merge is a promotion. If you let an agent-written diff jump from “tests passed on my laptop” to main , you skipped th…
How much faster is macOS CI on dedicated runners? Five open-source projects, measured
Originally published on the Manzanita blog . I work on Manzanita, one of the runners compared below — so weigh the source. I've tried to make every…
Don't Merge the First Green Check: Hooks, Fixtures, and a Flake Budget
A green check is a temperature reading. It is not permission to merge. You merge when three mechanical gates have already fired: a hook refused unde…
Classify the Failure Before the Agent Edits a Test
Core claim: A green run after an agent patch is not validation. It is a zero exit code from a suite the model was allowed to edit. Route every faili…
Putting GitHub Actions runners on your private network with NetBird
Sooner or later a CI job needs to reach something that is not on the public internet. A staging database, an internal container registry, a deploy t…
Freeze Agent-Patch Tests Against a Fixture Digest, Not a Name
A flaky freeze is valid for one fixture digest only. If an agent patch rewrites the bytes under a test, the old skip is evidence about a different p…
My CI has been red for 18 days. It never started a single job.
My CI went red on 2026-08-15 and it is still red today. For most of the time in between I read that colour as "the build is broken." It wasn't. The…
Properties First, Fixtures Second, Flakes Never: A Test Contract for Agent Patches
An agent patch is a hypothesis. A test suite is the only evidence a reviewer gets. Most suites fail at that job in three reproducible ways: assertio…