-
Notifications
You must be signed in to change notification settings - Fork 1k
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
chore: Refactoring release yamls to be more modular and remove redundancies #4826
Conversation
@franciscojavierarceo we probably need a way of ensuring that |
100% I'm just saving my code because I wanted to switch to fixing the images. This PR is draft, so feel free to ignore for now. I'll tag you when ready. 👍 |
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
…plement it Signed-off-by: Francisco Javier Arceo <[email protected]>
f13e3fb
to
25f4d4a
Compare
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
@tchughesiv @lokeshrangineni I've refactored the workflows and broken them apart into more reusable components. Can you take a look and see if I missed anything? |
Signed-off-by: Francisco Javier Arceo <[email protected]>
Signed-off-by: Francisco Javier Arceo <[email protected]>
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.
lgtm
What this PR does / why we need it:
Refactoring release yamls to be more module and not use redundant code.
Which issue(s) this PR fixes:
Misc