Skip to content
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

Check that reviewers actually exist #191

Open
Kobzol opened this issue Jan 1, 2025 · 3 comments
Open

Check that reviewers actually exist #191

Kobzol opened this issue Jan 1, 2025 · 3 comments
Labels
good first issue Good for newcomers

Comments

@Kobzol
Copy link
Contributor

Kobzol commented Jan 1, 2025

When someone does @bors r=abc, the bot should check if abc is a valid (GitHub) username (or a GH team?). To avoid situations where the name of the reviewer is mispelled, which happens quite often, and is problematic for https://thanks.rust-lang.org/.

It is common to specify names separated by commas, so bors should understand that and check all usernames separately.

We might also include some kind of opt-out, where you really want to use r= for a non-existent GH account.

@marcoieni
Copy link
Member

marcoieni commented Jan 16, 2025

We might also include some kind of opt-out, where you really want to use r= for a non-existent GH account.

what are the use cases for this? Imo we should document them 👍

Also, should we mark this as good-first-issue?

@Kobzol Kobzol added the good first issue Good for newcomers label Jan 16, 2025
@Kobzol
Copy link
Contributor Author

Kobzol commented Jan 16, 2025

Yeah, this shouldn't be hard, marked it as such :)

The use-case is mostly using r=, where the team might or might not be an actual GitHub team, and reviewers might not be willing to lookup the actual name of the team :D But marking a team as a reviewer is quite rare, tbh, so I think it would be fine if we just error out on an invalid name, and perhaps print a list of names that have a close Levenshtein distance (or something like that) to the used name.

@marcoieni
Copy link
Member

Ok, so it seems we could have two PRs to solve this issue:

  1. The first one, just checks for invalid @bors r=abc
  2. The second one, prints a list of names that have a close distance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Backlog
Development

No branches or pull requests

2 participants