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
code-generator: refer to the API package for GV{R,K} #113654
code-generator: refer to the API package for GV{R,K} #113654
Conversation
/triage accepted |
/lgtm |
@JoelSpeed we've talked about generators before. This change looks pretty reasonable to me, but it interacts with the API packages, have a look. /assign @JoelSpeed |
Yep I think this is ok. The API generators already rely on having a /lgtm |
/approve |
Thanks, folks! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, lavalamp, stevekuznetsov The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There should only be one source of truth for the API group's name and version. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
3bc7ed6
to
e13198e
Compare
/lgtm |
LGTM label has been added. Git tree hash: 92f51845a8479deecca3a121fc3c7308077d9521
|
There should only be one source of truth for the API group's name and version.
Signed-off-by: Steve Kuznetsov skuznets@redhat.com
It's not obvious to me what is causing the import alias renames, I'm assuming at some point the argument map gets sorted and the order is dependent on the values ... ?
/kind cleanup