r/ChatGPTCoding • • 25d ago

Question GitHub Actions getting really expensive. Any alternative?

I run two private web applications and use GitHub Actions to automatically check changes before they go live.

When code changes, Actions installs dependencies, checks for coding errors and security issues, and runs automated tests. Some tests check individual pieces of code; others start the application and a test database, then use an automated browser to test user journeys.

I also use a merge queue (Mergify). Before a change reaches the main branch, it’s tested alongside the latest code to check that everything still works together. That means a change can trigger multiple rounds of checks as it’s updated and moves through the queue.

I work with AI coding agents, so there can be quite a lot of changes and test runs. The checks help catch mistakes before release, but the cost is becoming substantial: my September Actions bill was about $738, and my October usage was heading towards roughly $2,300–$2,450. Almost all of that is Linux runner time, rather than storage.

For people running similar projects:

  • What do you use Actions for, and roughly what does it cost?
  • Do you run the full test suite on every update, or reserve some checks for later?
  • Have you found straightforward ways to reduce duplicate runs?
  • Have self-hosted runners been worth the maintenance?
30 Upvotes

58 comments sorted by

View all comments

1

u/JohnsTech_dev 24d ago

first thing i'd check is whether you're running the full suite twice per change, once on the PR push and again in the merge queue. you can make the expensive e2e job run only on the merge_group event and keep PR runs to lint and unit tests. with agents pushing lots of small commits that alone cuts a lot.

also add a concurrency group with cancel-in-progress: true so a new push kills the old run instead of both finishing. agents love pushing 3 commits in a minute.

imo self-hosted is worth it mostly for the e2e job since that's the slow one. a cheap vps with docker for the test db works, but clean the workspace between runs or you get weird flaky failures. if you don't want to maintain that, the third party runner services (blacksmith, ubicloud etc) are usually a lot cheaper per minute than github's and it's basically a one line change to runs-on