What AI Can Do with GitHub
Once connected, AI coworkers can:| Capability | Example Use |
|---|---|
| Read repositories | ”What’s the structure of our main repo?” |
| Search code | ”Find all files that use the auth service” |
| Create issues | ”Create an issue for the login bug we discussed” |
| Read issues | ”What are the open issues labeled ‘urgent’?” |
| Create pull requests | ”Open a PR with these changes” |
| Review PRs | ”Summarize the changes in PR #42” |
| Track activity | ”What was merged this week?” |
Prerequisites
Before connecting GitHub:- You need a GitHub account with access to the repositories you want to connect
- You must be a Trilo workspace admin (or have integration permissions)
- Your GitHub organization must allow OAuth apps (if connecting org repos)
Connecting GitHub
Select Repositories
Choose which repositories Trilo can access:
- All repositories - Access to all repos you have access to
- Selected repositories - Choose specific repos
For organization repositories, you may need organization owner approval before the app can be installed.
Configuring Repository Access
After connecting, configure which projects can use GitHub:Permissions Explained
| Permission | Why It’s Needed |
|---|---|
| Read code | To search code and understand repository structure |
| Read issues | To list and search existing issues |
| Write issues | To create issues from conversations |
| Read pull requests | To summarize and review PRs |
| Write pull requests | To create PRs when requested |
| Read repository metadata | To list repos and branches |
Using GitHub with AI Coworkers
In Project Chat
Ask AI coworkers about your code:In Tasks
When AI coworkers work on tasks, they can:- Reference related GitHub issues
- Create issues for bugs discovered during work
- Link PRs to task completion
In Workflows
Automated workflows can:- Monitor repositories for new issues
- Get notified of PR merges
- Create tasks from GitHub issues
Best Practices
Limit repository access per project
Limit repository access per project
Don’t give every project access to every repository. The marketing project doesn’t need access to the infrastructure repo. This keeps AI focused on relevant context.
Use for issue creation, not code changes
Use for issue creation, not code changes
AI coworkers are great at creating issues and summarizing code. For actual code changes, developers should push commits directly. AI can create PRs for simple changes if requested.
Keep sensitive repos separate
Keep sensitive repos separate
If you have repositories with secrets, credentials, or sensitive business logic, consider not connecting them. AI doesn’t need access to everything.
Troubleshooting
Can't see my organization's repositories
Can't see my organization's repositories
Your organization may need to approve the Trilo GitHub app. Ask an organization owner to approve it in Organization Settings → Third-party Access.
AI says it can't access a repository
AI says it can't access a repository
Check that:
- The repository is included in your GitHub app installation
- The repository is assigned to the project you’re chatting in
- Your personal GitHub permissions include that repository
Integration shows as disconnected
Integration shows as disconnected
The OAuth token may have expired. Click Reconnect in Trilo’s integration settings to re-authorize.
Can't create issues or PRs
Can't create issues or PRs
Verify that the GitHub app has write permissions. If you selected read-only during setup, you’ll need to update the app’s permissions in GitHub.
Disconnecting GitHub
To remove the GitHub integration:Security Considerations
- OAuth-based: Uses GitHub OAuth, not personal access tokens
- Granular access: You choose which repositories to share
- Revocable: Can be disconnected anytime from Trilo or GitHub
- Audit logged: Actions are tracked in task and workspace activity
