-
Notifications
You must be signed in to change notification settings - Fork 21
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
Refactor/global target flags #196
Refactor/global target flags #196
Conversation
@sven-petersen Thank you for your contribution. |
Thank you @sven-petersen for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below. |
cf836e8
to
21ff854
Compare
537eef0
to
c4fb334
Compare
@sven-petersen You need rebase this pull request with latest master branch. Please check. |
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 (but requires rebase)
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
Don't forget to rebase
c4fb334
to
2e2007b
Compare
2e2007b
to
1c40a21
Compare
7315c7f
to
19c104b
Compare
What this PR does / why we need it:
Instead of registering the target flags (
--garden
,--shoot
, ...) on the root cmd they are now registered per command. This way the flags are only available where they have an effect.Which issue(s) this PR fixes:
Fixes #85 (2nd step)
Special notes for your reviewer:
follow up: #195
Release note: