How did github gaslight everyone into thinking that putting random incarnations of scripts into a yaml file is a good way to do anything and there's no way to validate this locally - ThreadSky

About ThreadSky

xpaw.me • 24 days ago

How did github gaslight everyone into thinking that putting random incarnations of scripts into a yaml file is a good way to do anything

and there's no way to validate this locally

Comments

haglund.dev•24 days ago

I would recommend actionlint, it catches a lot of problems

nuro.dev•24 days ago

If you're referring to GitHub actions, I can only recommend using `act` to save you pushing commits to test
https://github.com/nektos/act

xpaw.me•24 days ago

I highly doubt they fully reimplement it with all the rules. There's no reason github can't ship their own validator.

psykzz.com•23 days ago

Workflows are only really docker containers or bash scripts. The only real problem is the ones that github provide using internal secrets like cache, those could likely be mocked though.

gtb3nw.bsky.social•23 days ago

There's a whole lot more actually. The problem with mocking is you might need it to work 😆

OIDC for example!

nuro.dev•24 days ago

IIRC `act` came about when Actions was in beta & since someone else in the community already made a tool to run it locally, afaik as near close to 1-1 with an action runner, why put in the effort to make one in house I guess? ¯\_(ツ)_/¯

mtranel.bsky.social•23 days ago

Always slice sections out as scripts and only do what's really only doable with the yml within the actual pipeline file.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply