Checking out remote branch (fast-forwarding local) scrolls to previous local commit.

[othrayte]

When checking out a remote branch that has an out of date local tracking branch fork fast-forwards the local branch (a fantastic feature BTW) but then fork scrolls to where the local branch was. For some of our fast paced repos this can be a long way from the where the local branch ends up after the fast-forward.

Steps to reproduce:

1. Create a branch (feature/A)
2. Push the branch to a remote (remote/feature/A)
3. Create another branch (feature/B)
4. Commit enough commits to feature/B locally to have feature/A offscreen, or near the bottom.
5. Commit to feature/A from another repo or the remote.
6. Fetch the remote. remote/feature/A should be at the stop of the screen, with feature/A at the bottom or offscreen
7. Double click on remote/feature/A to checkout feature/A and fast-forward.
   At this point the screen has scrolled down to where feature/A was before the fast-forward

[DanPristupov]

You didn't describe the expected behavior.

Update: ouch, sorry. I understand the problem.