-
Notifications
You must be signed in to change notification settings - Fork 3.4k
.github/workflows: add step 5 as part of the image build process #41113
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
Conversation
/test |
e3460a0
to
4036d47
Compare
/test |
4036d47
to
3a5dcde
Compare
/test |
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.
I'm a bit on the fence about whether this repository is the right place to host the logic for managing the merge, but on the other hand if it's part of this workflow which (a) has environment: release-tool
for appropriate approvals and (b) is tied into the same workflow we already monitor for progress, it's probably easier to track the status of the release through this workflow than to add more logic elsewhere.
Either way this seems like an improvement to the process that should simplify things moving forward. If we hit some problems with this approach we can always amend the process further. 👍
3a5dcde
to
22703ac
Compare
This will make the release process even more smooth for release managers. Signed-off-by: André Martins <andre@cilium.io>
22703ac
to
e9a0771
Compare
/test |
This will make the release process even more smooth for release managers.
Depends on cilium/release#348