Remote Sync

The remote sync option has been changed to an experimental feature when this issue was initially discovered.

When performing a sync, the first step is pull from the remote. If there's not been any changes, this'll currently report the local branch is already up-to-date by throwing an exception. Consequently, the sync operation doesn't move onto the next step which is to push local changes.

The branch already being up-to-date isn't actually an error, treating it as such was a workaround when this functionality was originally implemented.

To resolve this problem, the user interface needs improving to handle displaying such information/warning messages in a more passive manner, without throwing an exception, which'll allow calling operations like sync to continue with subsequent steps.