Setup merge automation for kubernetes-client repos

[spiffxp]

This will turn on /lgtm, /approve, and auto-merging via tide. Same automation
that's used by all repos in kubernetes-sigs and kubernetes-csi.

/sig contributor-experience
/area github-management
/kind cleanup
/sig api-machinery

/cc @brendandburns @mbohlool
You have admin/write access to most of the kubernetes-client repos

/cc @roycaihw @yliaog @dims @lavalamp
You have admin/write access to the rest (as collaborators). Since you're already kubernetes
members I'd encourage you to file a membership request for kubernetes-client
and mention that. The requirements/sponsors and PR/issue lists can be skipped in that case

/hold
for comment

This is the main audience impacted, so I'm not inclined to send a k-dev@ lazy conensus e-mail.
I'm most interested in hearing from @brendandburns and @yliaog as the most active mergers recently.

[dims]

LGTM (not using bot command so others can review)

[yliaog]

what is the reason for not listing other repos under kubernetes-client here too?

[spiffxp]

Based on my exploration of other repos' commit history, these are the only two repos that use the squash method, the rest use the default. If the desire is to move everything to squash, that is doable via PR. I'm also fine having these two repos use the same merge method as everything else.

My goal with this PR is to automate the state of today, and then back away and let you change as you see fit.

[roycaihw]

LGTM

[yliaog]

/lgtm

[brendandburns]

LGTM, this is great, thanks!

[brendandburns]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brendandburns, spiffxp, yliaog

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:

• prow/OWNERS [spiffxp]

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

[brendandburns]

/unhold

[spiffxp]

/hold cancel
deploying

[k8s-ci-robot]

@spiffxp: Updated the following 2 configmaps:

• config configmap using the following files:
  • key config.yaml using file prow/config.yaml
• plugins configmap using the following files:
  • key plugins.yaml using file prow/plugins.yaml

In response to this:

This will turn on /lgtm, /approve, and auto-merging via tide. Same automation
that's used by all repos in kubernetes-sigs and kubernetes-csi.

/sig contributor-experience
/area github-management
/kind cleanup
/sig api-machinery

/cc @brendandburns @mbohlool
You have admin/write access to most of the kubernetes-client repos

/cc @roycaihw @yliaog @dims @lavalamp
You have admin/write access to the rest (as collaborators). Since you're already kubernetes
members I'd encourage you to file a membership request for kubernetes-client
and mention that. The requirements/sponsors and PR/issue lists can be skipped in that case

/hold
for comment

This is the main audience impacted, so I'm not inclined to send a k-dev@ lazy conensus e-mail.
I'm most interested in hearing from @brendandburns and @yliaog as the most active mergers recently.

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.