-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish tag follow up #1536
Publish tag follow up #1536
Conversation
It should already be done by `ko resolve …` in a previous step. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
- Use `ko` to publish tags while resolving and building the image - Move `generate-release-version` task above to have the `VERSION_TAG` variable computed already. Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
323bdc3
to
7d38717
Compare
/cc @afrittoli |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIce, thank you!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli 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 |
Changes
Follow-up on #1502
gcloud
)pushblish-nightly.yaml
to do the same/hold
needs a rebase after #1502 gets merged 👼
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.