GitHub

Connecting GitHub lets Remergd list the repositories of a user or organization, clone them, publish new ones, and review, comment on, approve, create and merge pull requests. Open Accounts (or the account step in the first-run setup) and choose GitHub.

Git itself keeps signing in through Git Credential Manager; the account in Remergd is for GitHub’s web API. Remergd works with github.com. GitHub Enterprise Server is not supported yet.

Sign in with GitHub

Choose Sign in with GitHub. Remergd shows a short code and opens github.com/login/device; enter the code there and approve Remergd.

Remergd asks for two permissions: repo, to list, clone and review repositories (private ones too), and read:org, to find your organizations. An organization may have to approve Remergd before its private repositories show up; GitHub asks about that on the approval page.

If you do not see Sign in with GitHub, use a token instead.

Use a personal access token

Create a token on GitHub under Settings → Developer settings → Personal access tokens, then paste it into Remergd.

• A classic token needs the scopes repo and read:org.
• A fine-grained token needs read and write access to Contents and Pull requests, and read access to Metadata, Checks and Commit statuses.

Where your sign-in is kept

The token is stored in Windows Credential Manager under com.remergd.app. It is never written to Remergd’s database or logs, and it is only sent to GitHub.

To disconnect, remove the account in Accounts. If you signed in with GitHub, you can also revoke Remergd on GitHub under Settings → Applications.