All ideasMore in Work
Work

An automatic coding pipeline merged 67 pull requests in two weeks, then he shut it down

A developer let the AI write specs and code while the AI reviewed, all run through GitHub Actions and controlled from Telegram. Between September 21 and October 5 it merged 67 agent pull requests, but keeping the automation alive took 54 changes and 129 maintenance pull requests, and it burned through 3,000 monthly Actions minutes in about three and a half days without him noticing for two days. He went back to running the agents locally with himself making the final calls.

This only partly worked. Read what happened before you try it.

How it works

  1. The AI writes specs and code
  2. The AI reviews
  3. Agents fix issues and merge
  4. 67 pull requests merged in two weeks
  5. Maintenance grows to 129 pull requests
  6. Actions minutes run out unnoticed
  7. Pipeline shut down

Why it’s worth knowing

The pipeline worked and still lost: the upkeep cost more than the direct way of working it replaced.

Where it’s from

Summarized from a public post on reddit.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

WorkFind me 48 school-district customers and draft each pitch — one replied, booked and paidWorkA contractor talks measurements into his phone and QuickBooks sends the estimate in 45 secondsWorkSunday lesson planning went from up to six hours to fifteen minutesWorkThe AI audited my eBay store, found 28 listings going nowhere, and sold a bundle for me

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.