Remergd

Azure DevOps

Connecting an Azure DevOps organization lets Remergd list your projects and repositories, clone them, and show, review and complete pull requests. Open Accounts (or the account step in the first-run setup) and choose Azure DevOps.

Git itself keeps signing in through Git Credential Manager, as it does today; the account in Remergd is for the Azure DevOps web API.

Sign in with Microsoft

Choose Sign in with Microsoft and sign in with your work or school account in the browser. Remergd stays signed in and renews access on its own, so there is no token to create or renew.

Your organization may have to allow the app the first time; Microsoft shows that on the sign-in page. If you do not see Sign in with Microsoft, or your organization does not allow it, use a token instead.

Use a personal access token

  1. In Azure DevOps, open User settings → Personal access tokens and create a new token.
  2. Give it these scopes:
    • Code: Read & write
    • Project and Team: Read
    • Identity: Read
    • Work Items: Read & write
  3. Under Organization, choose All accessible organizations to let Remergd find your other organizations too.
  4. Paste the token into Remergd with the organization’s name.

Azure DevOps tokens expire. When one does, Remergd says so on the account, and you can paste a new token without connecting again. An account can also switch between a token and signing in.

Where your sign-in is kept

Tokens, and the access Remergd gets from signing in, are stored in Windows Credential Manager under com.remergd.app. They are never written to Remergd’s database or logs, and they are only sent to Azure DevOps.