Fetch UI action should only fetch upstream remote

[torarnv]

When triggering the fetch action from the UI it currently fetches from all remotes in the repo.

This is a bit surprising, given that the UI explicitly describes the upstream remote:

It also doesn't match the git fetch default behavior, which just fetches the upstream remote. GB currently behaves as if the user was doing git fetch --all, but doesn't seem to respect remote.<name>.skipFetchAll, which would allow the user to avoid fetching specific remotes.

[Byron]

Thanks a lot for reporting!

I agree that in an effort to become a good Gitizen, GB shouldn't avoid breaking with standard Git behaviour unless there is a very good reason to. Here, that might not be the case, or if it is, that would have to be communicated better.

Generally, GB's remote handling is a bit special right now and it doesn't necessarily respect Git configuration at all.