Closed davidstaheli closed 1 month ago
Should have been fixed by https://github.com/microsoft/vscode-pull-request-github/pull/4941, but it looks like I missed a spot where we try to check if a git remote is actually GitHub Enterprise.
@alexr00, gave this a try creating a pull request / refreshing and didn't see logs in the "GH pull request" output or the "Github" output channel. Where would I find the log to check and how would I ensure it is triggered?
The incorrect path was only being used when we try to figure out if your git remotes are actually GitHub Enterprise, so you'll need to sign out to verify.
To verify:
aaaaa.ghe.com
).I tried using my DevDiv EMU account but didn't see a modal dialog for step 4. I logged in through my browser instead.
EMU isn't the same as GitHub Enterprise Cloud. You need an account within that instance (ccc.ghe.com
). I think I should be able to verify this
Thanks @TylerLeonhardt !
GitHub is requesting for this to be addressed by October 4, 2024 if at all possible, to ensure a seamless experience for users of this extension.
*.ghe.com
Steps to Reproduce:
GitHub logs show that recent API requests using the user agent "GitHub VSCode Pull Requests" targeted URLs with
/api/v3
in the path, such ashttps://my-name.ghe.com/api/v3/users
. The/api/v3
pattern is specific to GitHub Enterprise Server and isn't supported on github.com. Soon, it will also no longer work on*.ghe.com
(please contact @davidstaheli and @eyalgal, GitHub PMs, for timing details). Instead,*.ghe.com
hosts should be treated like GitHub Enterprise Cloud and theapi.
domain prefix should be used, similar to with github.com, such ashttps://api.my-name.ghe.com/users
. Thank you!