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.

  • smeg@feddit.ukEnglish
    24·
    3 days ago

    If you can test it on a feature branch then at least you can squash or tidy the commits after you’ve got them working. If you can only test by committing to main though, curse whoever designed that.

    • ulterno@programming.devOPEnglish
      2·
      3 days ago

      Well, it does have triggers for other branches:

      on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

      So, most probably would have a way to run it on other branches.

      • odelik@lemmy.today
        7·
        3 days ago

        You can also use the workflow_dispatch execution pattern and use some data input params and execute through the portal interface.

        However, do be careful about trusting input params without sanitizing them (GH has docs around this).

        • ulterno@programming.devOPEnglish
          1·
          2 days ago

          Thanks, I’ll look into that.
          While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on