Connect GitHub: sign in with GitHub, the gh sign-in, or a token

In NeuralVault 2.0 the GitHub card at the top of Settings, Connectors and integrations connects the assistant to your repositories, issues and pull requests. Signing in with GitHub is in Test builds only for now; reusing the gh sign-in on this computer and pasting a token work as before.

Last checked against the app on · View as Markdown

Steps

  1. Open Settings, then Connections and data, then Connectors and integrations. The GitHub card sits at the top. Its pill reads "Not connected" until one of the ways below works.
  2. Sign in with GitHub (Test builds only for now): press "Sign in with GitHub". The app shows a short code and opens github.com/login/device. Type the code there and approve. While it waits the card reads "Waiting for you on GitHub" and has a Cancel button. You sign in as yourself, and the sign-in is kept only in this computer’s credential store. It renews itself and is never sent to a NeuralVault server or the model.
  3. The gh sign-in: if the GitHub CLI is installed and signed in, press "Use my GitHub CLI sign-in". This stores nothing, and the assistant asks the gh command for the sign-in whenever it needs one. If gh is missing or signed out, run gh auth login in a terminal and press "Check again".
  4. A token: choose "Paste a token", paste a fine-grained or classic token and save it. It goes into this computer’s credential store. The card suggests these permissions: Contents read, Issues read and write, Pull requests read and write, Metadata read.
  5. When it works the pill reads "Connected as" followed by your account, and the card shows what it signed in with and what it can do. "Test connection" checks it again.
  6. The assistant reads repositories, issues, pull requests, files, commits and releases. Creating, commenting on and editing issues, opening, reviewing and merging pull requests ask you on a card every time.
  7. If more than one is set up, the assistant tries the GitHub sign-in first, then a pasted token, then gh.
  8. To disconnect, press "Sign out" (or "Disconnect" for a saved token) and confirm. This removes only that sign-in from this computer. To revoke the app on GitHub too, use github.com/settings/applications. A gh sign-in on this computer would still be used until you run gh auth logout.

How to tell it worked

The pill reads "Connected as" with your GitHub account name, and asking the assistant to list your open pull requests returns them.

If it does not work

There is no "Sign in with GitHub" button.
The button is in Test builds only for now, so a public build does not show it. Use the gh sign-in or a token meanwhile.
The card says "GitHub needs attention".
Read the message under it. It is GitHub’s reason, such as a token that has expired or lacks a permission. Replace the token or sign in again.
The code ran out of time.
Press "Sign in with GitHub" again to get a new code.
You disconnected but the assistant still reaches GitHub.
The gh command is still signed in on this computer and is used as a last resort. Run gh auth logout to stop that.