-
Notifications
You must be signed in to change notification settings - Fork 588
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
No PR changes displayed for a specific repo on any PR. #6513
Comments
@mikebronner is this with GitHub Enterprise? |
I don't believe so. This is the org: https://github.com/CrossBibleInc |
Is it a private repo in https://github.com/CrossBibleInc? |
yes |
I think something might be wrong with your auth token. Could you try the following:
|
I have tried that several times in the past, and just now again, issue persists. I do not believe it is my GitHub connection settings in VSCode, as other repos in other organizations work just fine. |
This is precisely the reason I do think it's an issue with your auth token, as different orgs can have different auth requirements. When you sign in to GitHub through VS Code, do you get taken to GitHub web page that asks about single sign on? For example, with the orgs that I belong to, this is the one that I see. |
Hmm. You don't see any other page after hitting continue? @TylerLeonhardt do you know of any way @mikebronner could check if the auth token they have for GitHub in VS Code is missing the access required for a public org's private repos? |
Hmm this doesn't really add up to me. These tokens shouldn't have access to only some orgs unless this organization uses SAML (aka Single Sign On) but if it did, you'd get the screenshot that @alexr00 shared. @alexr00 can we get any more details on this error besides "HttpError: Server Error"? Also, doesn't that usually mean 500 so this would be a GitHub API bug? |
git clone .....
Steps to Reproduce:
The output panel for Github Pull Requests extension has the following output:
Unfortunately there aren't more details that would indicate the precise error that is being shown in the API calls. Anything I can do to investigate this better, perhaps make some API calls using curl? I would need guidance on exactly which commands to run.
The text was updated successfully, but these errors were encountered: