You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working on stacked PRs it's common to want to address comments on a lower PR in the stack while having the branch from a higher PR checked out.
At the moment it seems that GithubPullRequests extension will not allow this even when a PR file or diff is opened in preview mode from the Pull Requests sidebar.
IMO the comments should still appear in these editor windows at the very least, and ideally in any file with comments.
The text was updated successfully, but these errors were encountered:
Sometimes I can see the comments and sometimes I cant see the comments when opening the file from the pull requests panel. (the editor says file_name.cc (Pull Request))
It seems like the first time I open the file after restarting VsCode, the comments are visible, but if I close and re-open the editor tab, they disappear and never come back until I restart vscode.
I've tried with both insiders (1.97.0-insider), and normal vscode (1.96.2) and have tried with both the release (0.102.0) and pre-release (0.103.2024121904) version of the vscode-github-pull-requests extension with no difference in behavior.
It is a bug, and apparently it's been around for nearly a year. Thanks for reporting!
alexr00
changed the title
View PR comments when on stacked PRs/branches
Comments don't show on non-checked out PR when closing and re-opening the file from the PRs veiw
Dec 20, 2024
When working on stacked PRs it's common to want to address comments on a lower PR in the stack while having the branch from a higher PR checked out.
At the moment it seems that GithubPullRequests extension will not allow this even when a PR file or diff is opened in preview mode from the Pull Requests sidebar.
IMO the comments should still appear in these editor windows at the very least, and ideally in any file with comments.
The text was updated successfully, but these errors were encountered: