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

Wrong comparison order in the Compare view when using Compare [HEAD|Working Tree] With comands #821

vabc3 opened this issue Aug 20, 2019 · 2 comments


Copy link

commented Aug 20, 2019

Is there an option to keep the old behavior.

For example, I do a change in branch 'my1', and then use the comparion tool to compare with 'origin/my1'.

For old behavior, the diff is origin/my1..my1, which makes more sense. This shows what I'm going to push to remote.

For new behavior, the diff is my1..origin/my1, which is not what I expect


This comment has been minimized.

Copy link

commented Aug 20, 2019

@vabc3 When you say comparison tool -- what do you mean? Creating a new compare from the Compare view? The Branch comparison node in the Repositories view? Selecting a branch and choosing Select for Compare and then selecting another and choosing Compare with Selected?


This comment has been minimized.

Copy link

commented Aug 21, 2019

It is F1->
(old version)'GitLens: Compare Working Tree With Branch Or Tag'
(new version)'GitLens: Compare Working Tree With'

@eamodio eamodio added the type: bug label Sep 3, 2019
@eamodio eamodio self-assigned this Sep 3, 2019
@eamodio eamodio added this to the Soon™ milestone Sep 3, 2019
@eamodio eamodio changed the title Regarding 'Reverses the order of comparisons in the Compare view for consistent comparisons results' Wrong comparison order in the Compare view when using Compare [HEAD|Working Tree] With comands Sep 3, 2019
@eamodio eamodio closed this in 71cfcbc Sep 20, 2019
@eamodio eamodio removed this from the Soon™ milestone Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.