-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: add default value for status-check flag when no value is specified #7278
fix: add default value for status-check flag when no value is specified #7278
Conversation
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.
Can we add a test for this?
@briandealwis Yes, do you think we should add a test for all NoOptDefValue flags? |
Codecov Report
@@ Coverage Diff @@
## main #7278 +/- ##
==========================================
- Coverage 70.48% 68.51% -1.98%
==========================================
Files 515 560 +45
Lines 23150 26507 +3357
==========================================
+ Hits 16317 18160 +1843
- Misses 5776 7094 +1318
- Partials 1057 1253 +196
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
…hout a value passed
This flag broke downstream consumers, so it seems worthy of some tests to ensure it doesn't happen again. |
@briandealwis I included a test in this PR to ensure that skaffold runs with these flags passed in with no value 👍🏼 |
Can we please leave this now as is, thanks for adding tests to make sure this doesn't break again. But now our pipeline broke twice:
|
Fixes problem addressed here: https://github.com/GoogleContainerTools/skaffold/pull/7089/files#r845391034
--status-check
can now be used without specifying={true|false}