gh pr edit --add-{reviewer,assignee} shouldn't need the organization.read scope #11920
Closed as duplicate of#4844
gh pr edit --add-{reviewer,assignee} shouldn't need the organization.read scope #11920
We have a GitHub workflow that updates a PR, tagging a new person (as both reviewer and assignee) when certain conditions are met.
This workflow is failing because we're calling
gh pr edit $pr --add-reviewer $username --add-assignee $username, and it is trying to read team members, even when we're just passing it a username.The underlying APIs do not need this scope (1, 2), so
ghshouldn't either (or at least should handle it gracefully when it isn't available).Our workaround is to just tag the user in a comment to the PR and skip assigning it to them.