Until he actually had to use it.

Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can’t see the container.

  • odelik@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    Unless I’m doing a simple bash or pwsh script, I prefer to use GHA Script due to the headaches caused by how things are translated down and missing quotes/slashes/etc can cause massive headaches.

    I’ve been meaning on spending a morning getting Nektos/ACT running.

    • ulterno@programming.devOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      I’ve been meaning on spending a morning getting Nektos/ACT running.

      I was just going to say I need to find a way to run it all on my system to learn it. If this can do it without actually having to push to GitHub, it would be really good for practice.

      • Traister101@lemmy.today
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 days ago

        Act works out pretty good but you need to pass it a token and stuff so the actual github CLI bits can work which is kind of a hassle. It took me much too long to discover you need a classic token, the one from the github CLI app gh auth token won’t work.

        Edit: Ah! Also getting act setup involved getting docker setup which involved me enabling virtualization in my bios for what I swear is like the 4th time I’ve done so. Also because I’m on Windows (iirc at least) I had to setup WSL or just make a windows container ಠ_ಠ

        • tyler@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          14 hours ago

          You also need to know what the internal GitHub event json looks like. Using act was such a pain I just gave up. Have tried several times now and it’s just easier to create a second repo just for testing and overwrite it with your current repo anytime you need to do major workflow changes.