@MGS-SEBASTIEN,

I agree something like this would be nice. Not having the latest commits locally is something that regularly trips me up.

There is an extension by @madskristensen that tackles your first suggestion (it's currently VS 2019 only).

I started working on a PR to add VS 2017 support and make it update all branches (not just the current one).
madskristensen/GitPull#3

If you're interested in trying this version, you can find the .vsix here:
https://ci.appveyor.com/project/madskristensen/gitpull/builds/21339372/artifacts

I'm a little hesitant to do thing anything automatically that make changes in the users working directory. I wonder is simply having a notification when there are remote chances would make more sense? The user could then click on the notification, see the incoming changes and update their repository. That way they'd always be aware of the latest commits.

Hi!
@jcansdale the problem is that git pull extension by @meaghanlewis performs pull which is not the case the person is asking.

As you know pull do the following:

1. fetches
2. merges
   So I would've preferred to have extensions doing the fetch instead of the pull.

Fetch is usually used in the git workflows and it makes really big problem for some people to go and fetch repo, which leads in their confusion not seeing the changes from remote.

Notification make sense, but I would've preferred a checkbox enabling me to do auto-fetches. I'm using the same feature in vscode (link) and it is awesome cos it reduces a lot of hassle.

Just to be clear, pulling is entirely out of the questing. This is only about auto-fetching.

would be good to see this, can trip over dev especially when they start out or are used to TFVC.
Two options, Auto Fetch or Auto Notify.