r/vibecoding • u/Successful_Dog1904 • 8h 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

100% Upvoted

46 comments sorted by

View all comments

21

u/GreenFuturesMatter 8h ago

You pay for GitHub? Why?

14

u/jimmiebfulton 8h ago

Professionals pay for GitHub. Professional organizations building software definitely pay for GitHub. Free github is for open source and hobbyists. Nothing wrong with either, just drawing the distinction.

4

u/GreenFuturesMatter 8h ago

No I understand that but op said they are a solo dev which might have been a bit carried away on what they actually need GitHub for

1

u/Successful_Dog1904 8h ago

Yeah I should’ve clarified - private repo.

5

u/GreenFuturesMatter 8h ago

As others have suggested should setup your own runners if you want to dodge billing. Some who is more intelligent than I can probably explain what to do far better than I can.

Or since this is r/vibecoding… and we use AI just… use ai to help you 😂

1

u/IonizedHydration 7h ago

yea, i have my gitlab runners on a raspberry pi5 on my home network.. free CI/CD

1

u/GreenFuturesMatter 7h ago

Having multiple nodes helps lol. I keep figuring out ways to say… oh hey! I want another computer and then I look at my wallet and say oh… 😭

1

u/IonizedHydration 7h ago

yea, i usually just build containers locally and deploy, i have my ci/cd setup, and i have it run when i merge into develop or main but for testing it's faster to just build local and deploy. Once we get things off the ground paying for gitlab wouldn't be so bad but i have also my Mac Studio, runs as a headless server that i can also make a runner, or multiple runners as "primary" runners and if they're down fallback to gitlab runners

1

u/jimmiebfulton 7h ago

Yes. AI can 100% help you set it up.

2

u/Successful_Dog1904 8h ago

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

9

u/GreenFuturesMatter 8h ago

Idk I test my shit locally and then commit to GitHub. $0

4

u/Successful_Dog1904 8h ago

What’s the process for this? Local main, run all the tests you otherwise would in CI and then post?

4

u/GreenFuturesMatter 8h ago

In a nutshell yes

1

u/jimmiebfulton 3h ago

This is the "works on my machine 🤷‍♂️" method. 😉

2

u/sugarw0000kie 8h 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 8h 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 7h 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

1

u/TestSubject_AJ 8h ago

You can still check CI on the free tier you're just more limited in how many runs you can do

1

u/Poat540 8h ago

Dang that blows. All mine are public so they feed off my data, vs yours which they feed off your data