Better UX for GitHub credential and timeout errors

[axosoft-ramint]

Currently, GitHub credentials errors and timeout errors pop up as annoying error notifications. The credential issue is related to 401s from GitHub queries, and the notification offers a "reauthenticate" option. But if it's a permissions problem or something, reauthenticating does not help. Even choosing to "hide notifications from GitLens" doesn't stop the notifications from popping up again the next time you load a window.

We need to surface these issues in a less invasive way and move away from the "error notification" pattern as it just creates friction for users, especially when using options like "reauthenticate" does not make the issue go away. We should still log them properly so that it can help us investigate when users have issues with integration features, but the UX needs to be improved.

[Roberto-Vizcarra]

We have determined that the issue is related to the re-authentication process for github.com integrations through gitkraken.dev .

We have a work around that can be used to resolve the issue while we fix it in a future release. To determine if the work around will work for you, you can try clicking the reauthenticate button. If you are redirected to a gitkraken.dev page that asks you to 'Add Additional Integrations', then the work around should work for you.

To resolve this, you will need to perform the following in order:

1. Log into https://gitkraken.dev/settings/integrations

2. Disconnect the current Github.com integrations

3. Reconnect the integrations

4. In GitLens navigate to their Remotes view and disconnect any GitHub remote they have by choosing the "Disconnect Remote Integration" icon and choosing "Disable & Sign Out".

   1. 

   2. 

5. You will then need to reconnect the remotes by choosing the "Connect Remote Integration" icon

   1.