GitHub Actions Pitfalls
fusectore.dev
GitHub Actions Pitfalls
1–10 of 111 posts
Re: GitHub Actions Pitfalls
#2The twice run workflow from "Push for all?" definitely happened to me, too. The others not so much.
In New projects I tend to use scripts to perform any required task for the ci and have github actions only run the script. Way easier to reason about.
Gitlab CI definitely handles this better with it "script" concept.
Re: GitHub Actions Pitfalls
#3If you want to run github actions locally before any pitfalls, you can try out
Re: GitHub Actions Pitfalls
#4I've used Github Actions at work for the past year and I'm a fan overall. The clearest sign of this is my feedback for improvement is almost entirely about missing features instead of broken ones. For examples, it'd be nice:
1. for Github to natively allow CI management for several repos in a centralized way, so repo setup can just be "select this CI config" instead of "copy this YAML file and change the project name in some places"
2. to mandate certain CI steps at the organization level (such as running `black`) so it isn't opt-in
Re: GitHub Actions Pitfalls
#5The twice run workflow from "Push for all?" definitely happened to me, too. The others not so much. In New projects I tend to use scripts to perform any required task for the ci and have github actions only run the script. Way easier to reason about. Gitlab CI definitely handles this better with it "script" concept.
Gitlab CI is really powerful.
Re: GitHub Actions Pitfalls
#6The UI for seeing logs is driving me insaaaane.
It's extremely slow and sluggish. Sometimes you have to refresh the page to see the actual latest line of the log.
Re: GitHub Actions Pitfalls
#7If you want to run github actions locally before any pitfalls, you can try out https://github.com/nektos/act
Ha, that's great, I am definitely trying it. Thank you.
Re: GitHub Actions Pitfalls
#8The most annoying thing for me is that a workflow_dispatch only workflow can't be launch manually until it's push into default branch as they are not listed. I can understand the Web-UI won't list them but even GitHub cli can't launch them. Once they appear in the default branch, only then you are free to launch them on any branch.
Re: GitHub Actions Pitfalls
#9Also a fun one is the "on" key that specifies when the workflow should run. "on" is magic in yaml, and some implementations will convert it to the string (!) "True" when it occurs as a key (I'm not talking about values here). This was a bit confusing when I tried to replace a hand-written yaml with a generated json ... They were identical, except for the on/True key. It's still not clear to me whether this is according to yaml spec or not, but in any case a json "on" key does work ... So I wonder, does GitHub Actions internally look for both "on" and "True"?
Re: GitHub Actions Pitfalls
#10The UI for seeing logs is driving me insaaaane. It's extremely slow and sluggish. Sometimes you have to refresh the page to see the actual latest line of the log.
It also regularly repeats the same line number. E.g. it numbers them 120, 121, ..., 131, 132, 120, 121, ...