SHIP-0038: Add Git Ref to Release Workflow #240
Conversation
Update the release workflow to accept a git reference as a parameter. This will be used to check out the appropriate release branch when generating artifacts and release notes. The workflow then creates a tag for the release, which is required by GoReleaser in a subsequent step. The action was also updated to use the (new?) inputs context, instead of relying on the inputs key existing in the github.events payload.
pull-request-size
bot
added
the
size/S
openshift-ci
bot
added
kind/cleanup
|
Note - I was able to successfully test the workflow on my personal fork. You can see the results in my release-v0.13.0-demo branch and the resulting v0.13.0-rc0 release. Note - the release notes didn't generate any content because I had not pushed tags to my fork in quite some time, and it expected the previous tag I provided ( |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SaschaSchwarze0 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
Changes
Update the release workflow to accept a git reference as a parameter. This will be used to check out the appropriate release branch when generating artifacts and release notes. The workflow then creates a tag for the release, which is required by GoReleaser in a subsequent step.
The action was also updated to use the (new?) inputs context, instead of relying on the inputs key existing in the github.events payload.
Part of #238
/kind cleanup
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes