News for hackers. Stuff that matters.
Re:Pricing Changes for GitHub Actions by fbcpck on Tuesday December 16, 2025 @02:29PM (#46293192)
I don't know how much of that 6 hours build is tangled up in github workflows, but if it's a single contiguous block, you probably could make it near zero by making the self-hosted runner do only the preparation and only the final upload process (workflow_dispatch when the build is complete).
Re:Pricing Changes for GitHub Actions by seniorThrowaway on Tuesday December 16, 2025 @03:45PM (#46294194)
Most of it is just time waiting either while the source assets are downloaded (I clean slate it, that's the point of CI after all), the build itself runs, or the artifact is uploading to it's storage home. I'm sure it could be re-architected to use less actions minutes but if I'm going to redo it I will probably just move away from actions altogether because it's only loosely linked to Github anyway (runs on a schedule) and that way I am insulated from any future changes they come up with. The hardest part will likely be figuring out the Slack bot posting, I do use the marketplace action for that, but that's probably low lift. With LLM assisted coding I'm leaning more and more to little in house apps for stuff like this, it keeps you from dealing with lock in and other extractive gotchas.
Re:Pricing Changes for GitHub Actions by maratc on Wednesday December 17, 2025 @03:27AM (#46299511)
Slack posting is literally one-line curl with a token. That's what the fancy marketplace action does behind the scenes.
Re:Pricing Changes for GitHub Actions by seniorThrowaway on Wednesday December 17, 2025 @12:54PM (#46302983)
Yep and a good example of how using the convenient best practice pushed by the vendor (the marketplace action) isn't a good idea. But I did.