search

project-codeflare / instascale

On-demand Kubernetes/OpenShift cluster scaling and aggregated resource provisioning
Apache License 2.0
10 stars 20 forks source link

Release workflow should open a PR with changes instead of direct push #117

Closed sutaakar closed 1 year ago

sutaakar commented 1 year ago

Right now the release workflow pushes the release changes directly into the branch. This approach doesn't work out of the box due to the branch protection in repository. As a result branch protection has to be disabled during release.

Release workflow should open a PR instead of pushing changes directly and wait until the PR is merged by OpenShift CI.

Also make sure that all created release artefacts (i.e. created release on GitHub and such) are removed in case release workflow fails.