News for hackers. Stuff that matters.
Re:The Pain That Is GitHub Actions by kelseydh on Thursday March 20, 2025 @04:03AM (#43420701)
Feel this pain so much. If you are debugging Github Action container builds, and each takes over ~40 minutes to build.. you can burn through a whole work day only testing six or seven changes.

There has to be a better way. How has nobody figured this out?

Re:The Pain That Is GitHub Actions by elAhmo on Thursday March 20, 2025 @04:26AM (#43420832)
There is act, that allows you to run actions locally. Although not exactly the same as the real thing, it can save time.

https://github.com/nektos/act

Re:The Pain That Is GitHub Actions by mab122 on Thursday March 20, 2025 @05:59AM (#43421304)
In organization setting this is almost useless if you are (or forced to) use some pre-made actions and/or actions that are for your organization only (they cannot be downloaded) also useless if you are forced to use self hosted runner with image that you don't have access to. Not to mention env/secrets and networking...
Re:The Pain That Is GitHub Actions by terminalbraid on Thursday March 20, 2025 @06:26AM (#43421457)
This is a great tool, but I always cringe when something so important comes from a third party
Re:The Pain That Is GitHub Actions by cantagi on Thursday March 20, 2025 @10:47AM (#43424228)
act is brilliant - it really helps iterate on github or gitea actions locally.
Re:The Pain That Is GitHub Actions by esafak on Thursday March 20, 2025 @04:45PM (#43428728)
There's dagger; CI as code. Test your pipeline locally, in your IDE.