You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
When someone does
@bors r=abc
, the bot should check ifabc
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.The text was updated successfully, but these errors were encountered: