GitHub
Connect GitHub with a personal access token or a GitHub App install.
GitHub is under Code and issues.
Connect
- Open Connected tools → GitHub → Connect.
- Choose Personal or Workspace.
- Pick Personal access token or GitHub App (OAuth install).
- Continue. For the App, approve the GitHub install. For a token, paste it in.
A fine-grained token needs every repository Stedia may use selected, with these repository permissions:
| Permission | Access |
|---|---|
| Contents | Read-only |
| Issues | Read & write |
| Pull requests | Read & write |
| Metadata | Read-only (GitHub selects it automatically) |
A classic token needs the repo scope.
If GitHub App is missing, this Stedia install has not configured the App. Token connect can still work.
Example prompts
Type one into a chat, or use it as a schedule's task.
- "List the open issues in acme/shop that nobody is assigned to, oldest first."
- "Summarize pull request #42 in acme/shop in three bullet points."
- "Open an issue in acme/shop titled 'Checkout button overlaps on mobile' with the steps from this chat."
Approvals
Reading (list issues, read a file) runs without a prompt. These actions ask first: create or update an issue, comment on an issue, create or merge a pull request.
If something goes wrong
- Stedia cannot see a repository: a fine-grained token only reaches the repositories you selected when you created it. Edit the token in GitHub and add the repository.
For problems every tool shares, see If something goes wrong.
Provider docs
- Authenticating to the GitHub REST API: where a personal access token comes from and what it can reach.
- About GitHub Apps: what the App install grants, and how to remove it.