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
I've found that when gh role is run in a forked repo, it queries data against the upstream (original) repo, rather than against origin (current, forked) repo:
> git remote -v
origin [email protected]:yermulnik/gh-repo-collab.git (fetch)
origin [email protected]:yermulnik/gh-repo-collab.git (push)
upstream [email protected]:mislav/gh-repo-collab.git (fetch)
upstream [email protected]:mislav/gh-repo-collab.git (push)
> gh role -f
yermulnik has read role in mislav/gh-repo-collab.
> gh role -u nedredmond
2023/04/29 14:19:13 unable to query nedredmond's role in mislav/gh-repo-collab: GraphQL: You do not have permission to view repository collaborators. (repository.collaborators)
In the example above origin is a forked repo which I own (and have full admin perms) and upstream is original repo that was cloned into yermulnik/gh-repo-collab.
My expectation is that gh role outputs info about current repository rather than about its "parent".
Thanks.
The text was updated successfully, but these errors were encountered:
I've found that when
gh role
is run in a forked repo, it queries data against theupstream
(original) repo, rather than againstorigin
(current, forked) repo:In the example above
origin
is a forked repo which I own (and have full admin perms) andupstream
is original repo that was cloned intoyermulnik/gh-repo-collab
.My expectation is that
gh role
outputs info about current repository rather than about its "parent".Thanks.
The text was updated successfully, but these errors were encountered: