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

Issue with forked repos #16

Open
yermulnik opened this issue May 2, 2023 · 0 comments
Open

Issue with forked repos #16

yermulnik opened this issue May 2, 2023 · 0 comments
Assignees

Comments

@yermulnik
Copy link

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.

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

2 participants