Closed asoorm closed 3 years ago
Love it.
@alephnull smth we talked about in context of manually running Github actions
To make sure I understand,
Have I got it right?
@alephnull that sounds perfect.
It may be better to just apply this logic to GoReleaser action anyway? I'll leave it to you to decide.
It may be better to just apply this logic to GoReleaser action anyway?
Yup, that's what I was thinking of doing. I'll remove the cut_release action.
https://github.com/TykTechnologies/tyk-operator/actions?query=workflow%3A%22Cut+Release%22
https://github.com/TykTechnologies/tyk-operator/blob/master/.github/workflows/cut_release.yml
We have a new GitHub action - called cut_release.
It is triggered manually from GitHub Actions.
We specify the version of the release we want to cut - and apply that to the master branch.
When we manually trigger the release, the action should:
This will trigger a goreleaser github action / build pipeline to push to Dockerhub - once master branch is pushed.
The current flow is a little manual & as such, if i forget to bump the Chart.yaml or something - then my release is broken.