Re:GitHub Actions Are a Problem
by remram on Sunday November 12, 2023 @10:56AM
(#38241249)
The problem is that GitHub Action offers a large ecosystem of reusable actions that you can't easily call from a script.
[ Parent
| on HN ]
I mainly ignore those - I stick to the actions that install things (setup-python) and run scripts.
You can get around the setup ones by using Docker images (e.g. run in python:3.11 rather than using setup-python).
Can you provide a link to an example?
The docs have examples: https://docs.github.com/en/actions/using-jobs/running-jobs-i...
Basically you set `container.image`.
You, you sacrifice that convenience for something purely in shell that is more portable.
you you?
It's like a yo-yo but faster
Re:GitHub Actions Are a Problem
by philipswood on Sunday November 12, 2023 @01:47PM
(#38242971)
Like yo-yo, but slower due to the extra W.
You should check out: https://github.com/nektos/act
Works pretty well for the actions I have used it on.
That's not a problem. You just don't use them if you don't want to suffer vendor lock.
> That's not a problem. You just don't use them if you don't want to suffer vendor lock.
How do you use GitHub Actions without using actions such as actions/checkout, actions/upload-artifact, actions/download-artifact?