4 ms·

The problem is that GitHub Action offers a large ecosystem of reusable actions that you can't easily call from a script.

• xeromal 3y ago
  You, you sacrifice that convenience for something purely in shell that is more portable.
  • remram 3y ago
    you you?
    • xeromal 3y ago
      It's like a yo-yo but faster
      • philipswood 3y ago
        Like yo-yo, but slower due to the extra W.
• simonw 3y ago
  I mainly ignore those - I stick to the actions that install things (setup-python) and run scripts.
  • remram 3y ago
    You can get around the setup ones by using Docker images (e.g. run in python:3.11 rather than using setup-python).
    • ddorian43 3y ago
      Can you provide a link to an example?
      • remram 3y ago
        The docs have examples: https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container https://docs.github.com/en/actions/using-jobs/running-jobs-i... Basically you set `container.image`.
• slenk 3y ago
  You should check out: https://github.com/nektos/act https://github.com/nektos/act Works pretty well for the actions I have used it on.
• jasonm23 3y ago
  That's not a problem. You just don't use them if you don't want to suffer vendor lock.
  • rewmie 3y ago
    > 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?