Skip to content
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

In review mode, the "Active Pull Request" panel contains another Pull Request #3508

Closed
faustnord opened this issue May 2, 2022 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@faustnord
Copy link

  • Extension version: v0.40.0
  • VSCode Version: 1.66.2 (Universal)
  • OS: macOS Monterey 12.3.1

Steps to Reproduce:

Снимок экрана 2022-04-27 в 17 25 25

Снимок экрана 2022-04-27 в 17 30 19

Снимок экрана 2022-04-27 в 17 33 47

Снимок экрана 2022-04-27 в 17 35 20

Снимок экрана 2022-04-27 в 17 39 40

Снимок экрана 2022-04-27 в 19 41 23

Снимок экрана 2022-04-27 в 19 43 57

Such non-obvious behavior leads to bad consequences. You think you're approving, commenting, or merging one branch (which you switched to), when in fact you're doing these actions on a completely different branch that you were working on before.

We've already gotten into trouble with this bug and accidentally merged a completely different branch that hasn't been finalized yet.

@dslatkin
Copy link

dslatkin commented May 2, 2022

Such non-obvious behavior leads to bad consequences. You think you're approving, commenting, or merging one branch (which you switched to), when in fact you're doing these actions on a completely different branch that you were working on before.

We've already gotten into trouble with this bug and accidentally merged a completely different branch that hasn't been finalized yet.

Not sure if it's related, but there's a similar issue in #3490 where there's a mismatch in the PRs displayed in the "Changes in pull request" and "Active pull request" panels. We've also been bitten with comments and approvals going to the wrong PRs. 🙁

@alexr00 alexr00 self-assigned this May 3, 2022
@alexr00 alexr00 added the bug Issue identified by VS Code Team member as probable bug label May 3, 2022
@alexr00 alexr00 added this to the April 2022 milestone May 3, 2022
@alexr00
Copy link
Member

alexr00 commented May 3, 2022

Thank you for the very clear repro steps! This looks like #3431.

I tried the steps with the current pre-release build of the extension (which has the fix for #3431), and wasn't able to reproduce the issue. If you're willing to try it out, instructions for using the pre-release build are very simple and are here: https://github.com/microsoft/vscode-pull-request-github/wiki/Pre-release-Build

@alexr00 alexr00 removed this from the April 2022 milestone May 3, 2022
@faustnord
Copy link
Author

I checked it.
This now works correctly in VS Code 1.67.0 and extension version v0.42.0

@alexr00
Copy link
Member

alexr00 commented May 9, 2022

Thank you for testing this @faustnord!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants