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.
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.
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.
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.
You can also use the
workflow_dispatchexecution 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).
Thanks, I’ll look into that.
While trying this time (as you can see in one of the commits), I added
workflow_dispatchat the wrong place, causing a problem. Later realised that it is part of theon