Move init container release from lambda to GHA #2932
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@hmstepanek Is there more to come for this PR, or are you ready to publish it? |
hmstepanek
force-pushed
the
move-release-from-lambda-to-gha
branch
from
50efdad to
a82244c
Compare
tippmar-nr
reviewed
Jan 15, 2025
tippmar-nr
reviewed
Jan 15, 2025
tippmar-nr
reviewed
Jan 15, 2025
tippmar-nr
approved these changes
Jan 15, 2025
chynesNR
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We are getting rid of the internal auto-layer-releases repo and moving creating of the release tags into each agent's GHA deploy flow.
Author Checklist
Reviewer Checklist