Skip to content

enhance: only navigate to upstream if current not ahead post-fetch #1581

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

NathanBaulch
Copy link
Contributor

@NathanBaulch NathanBaulch commented Jul 15, 2025

#1127 and #1180 introduced an annoying behavior when working in a branch that tracks an inactive upstream fork. Whenever I fetch latest, the history list scrolls down to the tracking branch even when the local branch is way ahead and no new changes were found for that tracking branch.

I don't know the ideal permanent solution to this, but this PR introduces an extra check to bypass history navigation if the current branch is ahead of the tracking branch. I'm not sure what should be selected post-fetch if there's a mixture of local and remote changes (ie, Ahead.Count and Behind.Count are non-zero).

@love-linger love-linger force-pushed the develop branch 6 times, most recently from 05dba32 to 6822ae3 Compare July 21, 2025 09:52
@love-linger love-linger force-pushed the develop branch 3 times, most recently from 072502a to 5ce919a Compare July 28, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant