<umarcor>
HackerFoo, litghost: if GitHub Actions workflows are based on containers and scripts, they are directly executable on any workstation, without needing act.
<HackerFoo>
umarcor: That doesn't help when it works on your machine, but not in CI.
<umarcor>
I'm sure it does, because act does not run the workflows in the same environment as CI. It uses containers which are "somehow similar". You can use those same containers locally.
<umarcor>
the point is that many workflows are not written taking that into account.
<umarcor>
mithro: it was working with Travis, but after you switched to GHA it does not create new releases anymore? instead, it uploads assets to the same all the time?
<umarcor>
so, using some "non-official" action is almost a requirement. the point is that you need to understand the action very well. at some point, it is easier to write a Python script that uses PyGitHub.
<umarcor>
precisely, eine/tip is a Python script that uses PyGitHub. in fact, MSYS2 used eine/tip at first, and then they used a custom script for better fitting their use case(s).
<umarcor>
given the requirements in Google or SymbiFlow, I think that writing a custom script using PyGitHub might be the best solution.
<umarcor>
before doing that, I need to understand what's your workflow, tho.