Test: dialog warning of stale repository due to uncommitted changes in RemoteHub

[joyceerhl]

Refs: microsoft/vscode-remote-repositories-github#115

• web @sandy081
• web @digitarald

Complexity: 2

Create Issue

---

This milestone we explored introducing a dialog to RemoteHub workspaces which alerts the user when they may be viewing an outdated version of their repository and guides them to sync their repository state before proceeding to work with their repository. Typically, RemoteHub users are shown the latest version of their repositories, but when users leave uncommitted changes in their repository, RemoteHub does not perform an automatic sync, since syncing can introduce merge conflicts.

Please test the following behavior:

1. Open insiders.vscode.dev to a GitHub repository
2. Make some edits to a file
3. From github.dev, commit to the same repo
4. Reload the insiders.vscode.dev tab
5. By default you should see a modal dialog highlighting that you have uncommitted changes in insiders.vscode.dev and are some commits behind
6. Test that the four actions "Sync", "Discard Changes", "Continue Without Syncing", and "Don't Show Again" behave as expected

The modal dialog is controlled by a setting: remoteHub.experimental.uncommittedChangesOnEntry. In pre-releases of RemoteHub, this setting defaults to promptIfBehind. Please test the following setting values and ensure they behave as expected:
a. promptIfBehind
- You should see a modal dialog only when you enter a workspace with uncommitted changes and have commits made to the current branch that have not yet been pulled
- You should not see a modal dialog when you enter a workspace with uncommitted changes that is up to date with the remote
b. promptAlways
- You should see a modal dialog when you enter a workspace with uncommitted changes, whether you are up to date with the remote or not
c. none
- You should never see a modal dialog even when you have uncommitted changes