Evaluate support for protected main/master branch #180
Description
Currently the releasescript cannot be used when the main / master Branch is protected as no direct commits to main / master are possible.
Eventually the releasescript could create a (temporary) branch, prepare everything for the release and create a PR. Releasing this PR could either be done manually or eventually by a workflow.
Not sure how tagging would work together with PRs as tagging triggers the normal test-and-release workflow for deploy.
Anyway support for protected main/master (requiring every change to be done using PR) would be welcome.