GitHub

GitHub can be connected in two ways; use either or both.

Settings → GitHub → Sign in with GitHub (or /github to the Telegram control bot) shows a short code. Enter it on github.com/login/device and confirm; the card then shows the account you're signed in as. No extra tools, no pasted token.

Signed in, ChatPilot uses that account for Questions for you, for tickets filed as GitHub issues and for reports about ChatPilot itself. Until then it uses the gh tool on this computer, if there is one.

It goes through ChatPilot's GitHub app, so it can only act on issues in repositories you installed the app on (Install it on your repositories on the card). Sign out (or /github signout) deletes the sign-in from this computer; to take the app's access away at GitHub itself, see GitHub → Settings → Applications.

Tickets as issues in a repository

To file tickets from chats as issues in a repository (a client's own repo, for example):

Settings → Connected systems → ＋ GitHub repository.
Type the repository as owner/name and click Add. ChatPilot checks that it exists, that it can reach it and that it takes issues.
Switch on its File a ticket action.

This needs ChatPilot to be signed in to GitHub (Settings → GitHub), or the gh tool set up on this computer. If it isn't, the form offers Sign in with GitHub and continues by itself. Issues filed this way are followed: a status change comes back with a suggested reply.

Bugs and wishes about ChatPilot itself already go to ChatPilot's own repository; no need to add that one.

Reading GitHub (MCP)

To let ChatPilot read issues, pull requests and code:

＋ Add system → GitHub (marked token).
Create a personal access token in GitHub: fine-grained, and read-only where you can.
Paste it as the API key and click Connect.

Signing in instead of a token would need a GitHub app of your own.

Their documentation: GitHub's MCP server.

Checked against ChatPilot 0.1.0b1. Report a problem with this page