-
Notifications
You must be signed in to change notification settings - Fork 587
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
Checked out PRs are not preloaded in VS Code desktop when using GitHub Repositories #4047
Comments
This appears to work correctly for PRs from forks, but not for PRs where the branch exists on the current repository. |
Interestingly, this works correctly if I use Open Remote Repository > Open Pull Request from GitHub but doesn't work if I right click on a PR from the GitHub tree view and select Checkout Pull Request. |
@joyceerhl do you mean that I don't think there's anything I can do from the GHPRI side to make the preload command call happen. What I can do:
|
@joyceerhl before I make this change: is there any plan to remove the window reload when checking a branch on desktop, since that would also solve this issue? |
I discovered that But for PRs on the current repo, GHPRI calls Alternatively, does GHPRI have code to check whether there is a PR associated with the current branch so it can independently decide to open the PR view even if RemoteHub isn't calling
This cannot happen without microsoft/vscode#35109 (though I'm unsure what blockers exist for that now). |
We already detect this, but we can't use it to open the view on reload as it would be overly eager and open on reload even when not checking out a PR.
I'll try it out and see. |
Passing |
This works as expected in web provided you're looking at a url like https://insiders.vscode.dev/github/microsoft/vscode/pull/163305, because the id
163305
gets passed in correctly. On desktop the id ends up being the branch name which is not correct, and that causes GitHub Repositories to not run the preload command to focus GHPRI's review mode. This is possibly an issue in GitHub Repositories, still investigating...The text was updated successfully, but these errors were encountered: