-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Problem with GitHub organization #63
Comments
@JDLH I ran into the same issue. Is the repository that you're trying to clone a part of a GitHub Organization? If so, you'll need to follow these instructions to allow OAuth access for git-credentials-oauth: #58 (comment) |
@andreobrown Thank you for the hint! Yes, the repo I am trying to access is related to a GitHub Organization. Specifically, it is my GitHub account's clone of the organisation's repo, and the repo contains a submodule which refers to another of the organisation's repos. Following the instructions at Requesting organization approval for OAuth apps, in the page for Application git-credential-oauth, under Organization access, I see the name of the owning GitHub Organization, and an "X" implying no access, and a "Request" button which I can push to ask the org to grant me access. If this turns out to be the underlying cause, then I may propose a Pull Request with an improvement to the git-credential-oauth documentation to cover this situation better. |
I have asked my organisation to approve my use of git-credential-oauth. If/when they grant it, and it works, I intend to report back here. For what it's worth, I filed a GitHub Docs issue #34710 Clarify use of OAuth credential helpers in local Git installation and Pull Request #34712 Patch for #34710, improving caching credentials with oauth mention. If those get accepted, then that may prevent future occurrences of this issue and #58 appearing in this project's issues list. |
Added documentation for GitHub organizations in 5be89d5 |
git fetch from my GitHub repo fails with "remote: Repository not found." despite apparently successful Oauth.
How to reproduce
% git credential-oauth configure
. Successful.cd
to local clone of a GitHub repo.git fetch
. Command prints (line breaks added for legibility):Observed behaviour
Command's output continues,
Git fetch does not occur.
Expected behaviour
No error message.
git fetch
succeeds.Discussion
The repository URL 'https://github.com/MyUserID/my-repo.git/' appears to be correct. I suspect that the repository is present on the remote, but that authentication was not acceptable to GitHub, and so they tell the command that it is not present.
Setting the helper command to
oauth -verbose
prints out lines beginning query:, token:, and output:, but does not give any kind of diagnostic reporting a failure.The text was updated successfully, but these errors were encountered: