-
Notifications
You must be signed in to change notification settings - Fork 504
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
Add goreleaser actions #3297
Add goreleaser actions #3297
Conversation
690136d
to
6d01fc1
Compare
6d01fc1
to
b804ef2
Compare
e045d41
to
5858c80
Compare
PTAL @kubernetes/release-engineering |
@saschagrunert There's a (strong) preference from SIG Testing and GitHub Admins to use Prow as much as possible. Why do we use GH Actions here instead of using Prow? We could more-or-less easily do everything in Prow. |
We already use goreleaser, for example in zeitgeist: https://github.com/kubernetes-sigs/zeitgeist/blob/master/.goreleaser.yml |
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.
thanks for that
just a few comments
/hold |
Signed-off-by: Sascha Grunert <[email protected]>
5858c80
to
96544ed
Compare
@cpanato addressed everything. PTAL again. |
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.
cool
lets run a release to try this out!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, saschagrunert 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 |
@cpanato can we lift the hold? |
/unhold sorry did not notice that :/ |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add a GitHub action to release the
release-notes
tool as well askrel
via goreleaser.Which issue(s) this PR fixes:
None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?