Reviewer configuration for k8s-ci-robot to make it not assign reviewers?

[illume]

Hello,

We moved into the kubernetes-sigs repo some months ago and are struggling with the increased pings caused by the k8s-ci-robot. Many of our PRs get all or most of our reviewers assigned.

Is there a way to configure the bot for our repo to not assign reviewers?

Repo in question is: https://github.com/kubernetes-sigs/headlamp

[BenTheElder]

Reviewers and Approvers are seperate fields. Please see the docs at https://www.kubernetes.dev/docs/guide/owners/ for how these work and how you can configure them (there should be a link to this in most OWNERS files in the org)

[BenTheElder]

You are explicitly configuring reviews to go to the maintainers (~=approvers?) and reviewers aliases:
https://github.com/kubernetes-sigs/headlamp/blob/d8241c14781b659f72224214d1f9b9ba9adeae70/OWNERS#L1-L7

You can add OWNERS files to specific directories to add reviewers for that specific area.

You could talk to sig contribex about disabling these mechanisms entirely, but there are standard assumptions about code review in the org and it's expected that an active and healthy project should have active reviewers.

This repo is lacking them, but the kubernetes org also can't very well archive it since it runs everything.

If it were another project, and we couldn't staff sufficient reviewers, the TLs of the SIG would be responsible to consider efforts to find sufficient maintainers to handle review assignment, or wind down the project.

[BenTheElder]

You could talk to sig contribex about disabling these mechanisms entirely, but there are standard assumptions about code review in the org and it's expected that an active and healthy project should have active reviewers.

To be more clear: Workflow changes are under their purview.

It is technically feasible to disable the plugin that assigns reviewers, I would suggest reconfiguring the OWNERS files first, but if you wish to pursue it then please reach out to contribex about disabling blunderbuss.

/close

[k8s-ci-robot]

@BenTheElder: Closing this issue.

In response to this:

You could talk to sig contribex about disabling these mechanisms entirely, but there are standard assumptions about code review in the org and it's expected that an active and healthy project should have active reviewers.

To be more clear: Workflow changes are under their purview.

It is technically feasible to disable the plugin that assigns reviewers, I would suggest reconfiguring the OWNERS files first, but if you wish to pursue it then please reach out to contribex about disabling blunderbuss.

/close

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-sigs/prow repository.

[illume]

Closed without discussion?

[BenTheElder]

@illume kubernetes/test-infra#35735 is a more appropriate place to follow up on changing the configuration, which is not up to the maintainers of this repo.

The technical capability exists and I can see you found the way to disable auto-assignment in your PR.

[illume]

Ok, I guess you want no discussion then.

[BenTheElder]

@illume , no, I just don't think there's anything further to discuss here? blunderbuss is the plugin, disabling it will disable reviewer assignment. As in kubernetes/test-infra#35735

We can discuss with contribex in kubernetes/test-infra#35735

BTW you can /reopen the issue if you want, but I don't understand what further you're looking for in this repo.

EDIT:
This repo contains the implementation of these tools. test-infra contains the configuration we have deployed.

SIG Contributor Experience is not active in this repo and it isn't the right place to discuss changing configuration.

We can discuss the proposed config change and alternatives further in kubernetes/test-infra#35735

[BenTheElder]

Some related resources:
https://prow.k8s.io/plugins
https://prow.k8s.io/command-help
https://docs.prow.k8s.io/docs/jobs/