Hacker News new | ask | show | jobs
by zufallsheld 1365 days ago
The 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.

2 comments

Yeah, I’ve lived through many a transition from one CI server to the next, so nowadays I just have CI call a script. You want to really minimize the amount you depend on a particular CI server’s features, to make switching very easy. Even if you never have to switch, it will be easier to maintain.
Gitlab CI is really powerful.