Use cases and repositories for github-comment-ops on jenkins-infra org

[lemeurherve]

Follow-up of #3060

As stated in this comment, github-comment-ops has been restricted to this repository only in the jenkins-infra organization.

Opening this issue to gather use cases for this tool in the context of jenkins-infra organization, and the repositories where it should be activated.

[lemeurherve]

For jenkins-infra here are my initial suggestions:

• keep all commands activated on helpdesk (as it's currently the case)
• activating the /reviewer command on all repositories can't harm I think, and would be useful especially on RPU and jenkins.io repo (needs Config based approach to commands timja/github-comment-ops#60)

[timja]

I think we could re-enable the bot on more repositories now? at least enable on one more, verify commands are disabled and then enable on all?

this would have {slash}reviewer active everywhere, and individual repositories could add more if they wanted

[lemeurherve]

I've enabled it on repository-permissions-updater & jenkins.io repositories.

[timja]

Works:
jenkins-infra/repository-permissions-updater#2697

[jetersen]

I know this says on jenkins-infra but still:
jenkinsci/pom#301 (comment) 😅

And here where @timja manually adds basil, which could have been a /reviewer:
jenkinsci/plugin-pom#596

[timja]

It’s only on limited repositories on jenkinsci currently