News for hackers. Stuff that matters.
Re:Release engineering is exhausting so here's cargo-dist by sedatk on Wednesday February 01, 2023 @02:54PM (#34616613)
You can run GitHub workflows locally with act: https://github.com/nektos/act
Re:Release engineering is exhausting so here's cargo-dist by frodowtf on Wednesday February 01, 2023 @03:17PM (#34616959)
Act is okay, but the runner image behaves quite differently than a GitHub runner would. The original image would just be too big for reasonable local workflows.

Also artifacts don't seem to be supported.

Re:Release engineering is exhausting so here's cargo-dist by netr0ute on Wednesday February 01, 2023 @08:39PM (#34620899)
> The original image would just be too big for reasonable local workflows.

Is there a way so I can still do this? I have terabytes of SSD just waiting to be used.

Re:Release engineering is exhausting so here's cargo-dist by ollien on Wednesday February 01, 2023 @03:03PM (#34616737)
This is far from perfect, IME. The big problem I have (and maybe there's a solution I don't know about) is that there's no easy way to test getting event data, unless you wanna rebuild the events yourself (which is hardly reliable if the problem is something like verifying a conditional that enables/disables a stage).
Re:Release engineering is exhausting so here's cargo-dist by adrienthebo on Wednesday February 01, 2023 @03:08PM (#34616797)
Seconding this; act has a lot of potential but misses a number of features such as support for deployment environment variables (eg `${{ var.DEPLOY_SPECIFIC_ENV_VAR }}`) and only recently added support for reusable workflows (https://github.com/nektos/act/issues/826). It looks like fine software and the maintainers deserve praise for their work but it's not yet a drop-in replacement for GitHub Actions.