Skip to content

Conversation

@t33m
Copy link

@t33m t33m commented Sep 4, 2021

... for testing purpose

@google-cla
Copy link

google-cla bot commented Sep 4, 2021

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-oss-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: t33m
To complete the pull request process, please assign illfelder after the PR has been reviewed.
You can assign the PR to them by writing /assign @illfelder in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-robot
Copy link
Collaborator

Hi @t33m. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@t33m t33m force-pushed the build_with_custom_endpoint_of_metadata_service branch from 315a98d to 9d1790d Compare September 4, 2021 14:36
@google-cla google-cla bot added cla: yes and removed cla: no labels Sep 4, 2021
@t33m
Copy link
Author

t33m commented Sep 21, 2021

@illfelder , @jaiminsh , @hopkiw , folks, plz, pay attention to this pr

@hopkiw
Copy link
Contributor

hopkiw commented Sep 21, 2021

/hold

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants