Today I played with GitHub Actions. Since I couldn't test anything without making a commit and pushing it to GitHub to trigger the workflow, my commit history now chronicles my slow descent into madness. Thank God it's a private repo. I'm gonna squash it if I ever make it public.

This gem is from hour two of my four-hour struggle:

As all cicd scripts without an offline linter do...

I had pages of "works!"/"work now?"/"please work!"/"fuck it"/"now!"/"shit!"

In a private git repo to study this shit.

This is normal, anything under 10 consecutive failures is a good effort.

I have used it recently and i quite like it. You can actually test your workflow locally with https://github.com/nektos/act. I suggest you check it out.

You can pass env vars and secrets that otherwise need to be picked up from your report secrets to the command line tool. It should save you from commits with fuck it, is it working?, Holy shit, what da fuck...

@AjDevNull thanks for the suggestion! Looks interesting

I haven't used it, but the docs say they support local action execution.

https://github.com/cli/cli

Unfortunately the particular job step I was troubleshooting was the step that was supposed to nicely format the output of previous steps and add it as a comment on the PR. I didn't even consider the idea of running it locally. I suppose I could have modified the step to convert the markdown to HTML and open it in a browser, but that might have ended up taking even more time...