Code & Dev Tools · Token
GitHub
Issues, pull requests, code search and repository files.
Ask your bot to…
- “List the open issues labelled bug”
- “Summarise what pull request #42 changes”
- “Find where we call the payments API in our repo”
How to connect
- 1
Get a personal access token.
Needs the repo scope (add read:org if the bot should see organisation repositories). Stored in your credential store, never in the workspace database.
Create a token on GitHub - 2
Open Connectors in Lobstack and choose GitHub. Paste it in.
- Default ownerOptional
- The GitHub account or organisation the connector is labelled with, so people sharing a workspace can tell whose GitHub it is. It does not limit what a bot can reach; the token decides that.
- Allow changesOptional
- Off, a bot can read issues, pull requests and code but not open, comment on, push or merge anything. A bot with a repository can still push its own branch without this.
- 3
Give it to a bot.
A bot reaches only the connectors you give it.
Tools
- search_issues
- get_issue
- create_issue
- list_pull_requests
- get_file_contents
Examples. The server decides the real list when it starts.

