4 ms·
Still no way to test action locally. This is especially troublesome considering that some actions only take effect once you have merged them into master. So i
by diveanon 5y ago
Still no way to test action locally.
This is especially troublesome considering that some actions only take effect once you have merged them into master.
So in order to develop an action that is using the on "delete" hook you need to disable CI on master, push your workflow to master, renable CI on master, switch to your dev branch and push a bunch of commits while iterating on your workflow.
https://docs.github.com/en/actions/reference/events-that-trigger-workflows#delete https://docs.github.com/en/actions/reference/events-that-tri...
Github what the fuck.
Don't even get me started on the "master" -> "default" name change... "master" in the git context isn't even being used in the "master / slave" sense.
Spend less time virtue signaling and improve your horrible CI and maybe I will consider bringing my projects back.
For those of you who are going to recommend I try the "act" library, I have, and after hours of debugging esoteric errors I just gave up.
- pood 5y ago100% agree. I have a dummy/empty/stupid action that does nothing that I copy pasta in and out of all the time. I have another action/workflow that literally checks that the master dummy action always does nothing. GitHub actions is very lacking in docs and setting up your own runners is very prone to generating cryptic errors that only appear on self hosted runners and it only gets worse inside of docker land.