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

Improve "Compare references" by not resolving references upon closing the two dialogs for the revision range #4114

Open
mx-bernhard opened this issue Feb 27, 2025 · 0 comments
Labels
triage Needs to be looked at

Comments

@mx-bernhard
Copy link

Description

I'd like to be able to compare the current branch versus the upstream version. For this I enter the values @ against @{u} in the dialogs that open from the command "Gitlens: Compare References...". This does work and is very helpful to immediately know what has changed on one side. The problem with this is: @{u} is resolved to a concrete git hash when the dialog closes for the revision.
When I switch to another branch I have to remove this compare references and create another one where I enter the same two values as above.

I'd like to be able just hit the refresh button on the compare references item in the "search & compare" view.

Is there a reason, this is resolved so early? On the other hand, branch references are not resolved and here this behaves as desired already. There are many ways to search for commits and there are probably more interesting use cases hidden behind this approach. Can it be toggled to resolve later?

@mx-bernhard mx-bernhard added the triage Needs to be looked at label Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs to be looked at
Projects
None yet
Development

No branches or pull requests

1 participant