At the time of creation, docker was the preferred solution to writing this action because there was no shell way of writing it.
Now it has arrived and we can rewrite to Composite run https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action
Switching to Composite run, one could also utilise the https://github.com/cli/cli which is included in the VM.
Cons to switching to this approach is that we will start to lack full control over the environment that we run the action inside. We are dependant on the Github Actions virtual environment.
At the time of creation, docker was the preferred solution to writing this action because there was no shell way of writing it.
Now it has arrived and we can rewrite to Composite run https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action
Switching to Composite run, one could also utilise the https://github.com/cli/cli which is included in the VM.
Cons to switching to this approach is that we will start to lack full control over the environment that we run the action inside. We are dependant on the Github Actions virtual environment.