-
Notifications
You must be signed in to change notification settings - Fork 170
Porridge/push upstream operator #18454
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
base: master
Are you sure you want to change the base?
Conversation
|
Skipping CI for Draft Pull Request. |
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.
Hey - I've left some high level feedback:
- In operator/tests/run.sh, consider quoting the operator_cluster_type in the conditional (e.g. [[ "$operator_cluster_type" == "openshift4" ]]) and explicitly handling unexpected/empty values so the deployment path is clearer and less error-prone.
- In .github/workflows/build.yaml, all uses of ${QUAY_ORG} assume it is set by earlier steps; it might be safer to set a default or add an explicit check/fail-fast if QUAY_ORG is unset to avoid pushing to an unintended registry when the matrix or labels change.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In operator/tests/run.sh, consider quoting the operator_cluster_type in the conditional (e.g. [[ "$operator_cluster_type" == "openshift4" ]]) and explicitly handling unexpected/empty values so the deployment path is clearer and less error-prone.
- In .github/workflows/build.yaml, all uses of ${QUAY_ORG} assume it is set by earlier steps; it might be safer to set a default or add an explicit check/fail-fast if QUAY_ORG is unset to avoid pushing to an unintended registry when the matrix or labels change.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
Images are ready for the commit at d492ca9. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #18454 +/- ##
==========================================
- Coverage 48.93% 48.92% -0.01%
==========================================
Files 2631 2629 -2
Lines 197964 197814 -150
==========================================
- Hits 96872 96788 -84
+ Misses 93703 93640 -63
+ Partials 7389 7386 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
change me!
User-facing documentation
Testing and quality
Automated testing
How I validated my change
change me!