Refresh DELETES ALL DATA if Vault is Synced to Different Gitlab Instance

[poetex]

If you are already using the Git community plugin to sync your vault to a gitlab/github server, and then you provide the Gitlab Issues plugin with an Auth Token from a different Gitlab instance, hitting the refresh icon to refresh the Gitlab issues will completely delete all files from a vault.

This is not a massive issue typically, since the user can just revert to the latest commit from the Git plugin's Gitlab instance remote server, or if it hasn't synced yet, all the deleted files are just marked as unstaged changes.

If the Git plugin's gitlab instance is down however, or if the sync fails for any reason, all the files that were deleted because of this bug moved from an unstaged changes state, to permanently deleted.

I didn't lose my entire vault, since my Gitlab instance went offline only a few hours ago, but everything I worked on from my last Git sync with the Git community plugin was deleted because of this bug.