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

Review bot error: Reviews may only be requested from collaborators #405

Closed
ggwpez opened this issue Jul 26, 2024 · 6 comments
Closed

Review bot error: Reviews may only be requested from collaborators #405

ggwpez opened this issue Jul 26, 2024 · 6 comments

Comments

@ggwpez
Copy link
Member

ggwpez commented Jul 26, 2024

CI from here:

gh: Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the polkadot-fellows/runtimes repository. (HTTP 422)
{"message":"Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the polkadot-fellows/runtimes repository.","documentation_url":"https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request","status":"422"}
Error: Process completed with exit code 1.

cc @Bullrich

@seadanda
Copy link
Contributor

seadanda commented Jul 29, 2024

Looks like this is related to the migration to the People Chain - identities are off the relay and now the bot thinks that nobody is a collaborator (there are no Github handles where it's looking). I haven't looked into the bot code yet but if you look at the logs for the "Get github handle of the fellows stage" it doesn't even connect to Polkadot People.

Also compare that stage of the action to the most recent PR merged to main which must have run before the identities were removed and you can see that #381 doesn't find the Github handles, but the stage is still passing. It then fails later because nobody who has reviewed it is in the list of ""s.

@seadanda
Copy link
Contributor

Looks like it is now fixed: paritytech/review-bot#131

Pending release and confirmation that this is the same cause

@ggwpez
Copy link
Member Author

ggwpez commented Jul 29, 2024

Yea waiting for approvals here now: #409

@bkchr
Copy link
Contributor

bkchr commented Jul 29, 2024

I have seen the error message before. The migration also happened at the 28th AFAIK.

@seadanda
Copy link
Contributor

Yea the same error would be triggered if somebody outside the fellowship (or not listed as a collaborator) reviewed the PR before it was changed.
Seems like getting the list of collaborators from the GitHub API and then using it to filter the list of reviewers before re-requesting a review would sort it.

@ggwpez
Copy link
Member Author

ggwpez commented Jul 31, 2024

Fixed not it seems.

@ggwpez ggwpez closed this as completed Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants