Skip to main content
All CollectionsTroubleshootingConnections and authentication
Change source control and services connections in Gearset
Change source control and services connections in Gearset

This article explains how to change or re-connect your source control service(s) in our app. We help you resolve common connection issues!

Richard Terry avatar
Written by Richard Terry
Updated over 4 months ago

Why can't I change my source control / services connection integrated with Gearset?

You may need to change the source control or service that you have connected with Gearset.

When you try to add the new connection, Gearset will automatically connect to your old repository or service.

This happens because the connection information is cached in your browser and is automatically used to login again with your old credentials.

Connect a new repository or service

In this example, we're showing how to re-connect GitHub. However, the process is identical for all repositories and/or services (such as Bitbucket, Gitlab, Azure DevOps, AWS CodeCommit, Jira, or Asana).

  1. First, remove the connection to GitHub.

  2. Log out of Gearset.

  3. Open GitHub in another browser tab and sign out of GitHub.

  4. Sign back into Gearset and reconnect GitHub. This will request your new login details.

Note: If Gearset still automatically connects after signing out of GitHub, disconnect GitHub again and open Gearset in an Incognito window. Then add the new repo from the Incognito window.

If you have any further questions, please contact us via the in-app chat, and we'll be able to help and advise further.

Did this answer your question?