Configuration issues when adding a remote to an already existing repository

Experienced with a customer this morning.
- Initialize a local git repository
- Add a remote to the git repository

You can get really wrapped around the axle if you do this and there's no way to resolve it except with direct access to the Git repository. There are some ways we can make it less painful.

- There are no remote branches locally, so the "remote branches" sidebar in the Web UI does not load. However you need that sidebar to fetch the remote branches. Workaround: do a "git fetch" in terminal. Fix: we should display the "remote branches" sidebar if a remote is configured, even if there are no remote branches locally.
- The local branches are not tracking the right remote branches. The resolution in this case is to switch to a new branch, delete the orphaned branch, and checkout the remote branch. Consider adding a warning to the Web UI if there is a remote configured and a local branch is not tracking a remote branch.