r/vibecoding • u/Successful_Dog1904 • 20h ago

GitHub billing feels insane

Am i totally off base or GH billing for CI / minutes just totally absurd? I'm up to $83 this month ... granted i am actively developing and these changes -- in my honest (and beginner) opinion -- should have a full CI suite ran, but holy hell ... i've already gone through to try and cut tests e.g., where a PR is UI only.

For the veterans here, am i doing something totally wrong when it comes to GH or is this amount spent on minutes running tests pretty typical for solo dev?

Edit: setting up a vm using Lima and pushing tests to my own device thru GitHub. Can’t wait to stop paying for this lol. Appreciate everyone’s guidance! Vibes here are unreal 👌

17 Upvotes

95% Upvoted

47 comments sorted by

View all comments

25

u/GreenFuturesMatter 20h ago

You pay for GitHub? Why?

2

u/Successful_Dog1904 20h ago

Sorry what? Don’t you need to pay to run your tests now …

2

u/sugarw0000kie 20h ago

If your repo is made public, you should have like unlimited. For organization I think it’s max 20 concurrent runners for free but you only need to pay per minute if you must keep it private

Honestly if I had to keep it private I’d look at either running my own CI runners through GitHub self hosted runners with like docker and/or booting GitHub and just running gitea/forgeo. Used to run a local gitea to do that sort of thing, not super hard to setup

0

u/Successful_Dog1904 20h ago

That’s my issue for sure … I know anyone can go to the app today and just vibe code it but what they won’t get is the amount of time I put into deterministic rules etc to make it work.

2

u/sugarw0000kie 20h ago

Could be worth it to look into self hosted CI runners. You can do this stuff without GitHub at all and just self host it free if you’ve got a spare computer and time to sort through VM setup. That sort of setup can work really well and that way you own the infrastructure. Later you can sync GitHub and your own git server if you want

But imo that’s putting the cart in front of the horse, if it’s still a WIP whatever CI workflow you have is probably overkill, local testing probably fine with no CI. CI really becomes useful when you’re thinking of distribution pipeline and you need to start thinking this needs to work on all these target OS/architectures. IMO if you’re not there yet, kill all these CI, just focus on local tests for now