GitHub integration for AI agents in team chat
Connect GitHub to Ando so agents can read repositories, triage issues and pull requests, check CI, and open changes from the conversation.
What agents can do in GitHub
With a GitHub connection, an agent that Ando runs can search and read repositories, files, commits, and branches; search, read, create, and comment on issues and pull requests; inspect pull request diffs, reviews, and CI check runs; create branches and commits, and open and merge pull requests; and look up organization members, teams, and releases. What an agent can actually do is limited to what the connected account and the selected repositories allow.
Connecting GitHub
Open Studio, then Apps, then GitHub, and start a connection. For shared repositories choose a workspace connection: you follow the GitHub App setup, choose the account or organization, and grant access to the repositories you want to use. Back in Ando you review the selected repositories and give the agent access. For your own account choose a personal connection and supply a GitHub personal access token; its actions use your GitHub permissions, and you enable it on an agent from the agent's Access tab.
Repository access has two boundaries
What GitHub grants the connection, and what you allow in Ando. A connection can be limited to selected repositories, and individual tools can be turned off. Giving an agent access does not override repository restrictions, branch protection, or required pull request reviews. If an organization requires approval for app installs, an organization owner has to approve it.
GitHub events in a channel
GitHub can also send signed events to Ando. A workspace admin or owner creates an inbound source for GitHub with the Ando API, pastes the returned URL and signing secret into GitHub, and routes the source into a conversation. You can route every supported event or only the ones you pick: an issue opened, closed, reopened, assigned, or labeled; a comment on an issue or pull request; a pull request opened, closed or merged, reopened, marked ready for review, sent for review, or reviewed; a release published; and a workflow run completed. There is no settings form for this today; it is set up through the API.
In a conversation
Mention the agent in the channel where the work is being discussed and ask it to read an issue or pull request from a selected repository. Start with a read to confirm access before you ask for changes. The answer comes back in the thread, where the rest of the team can see what the agent found and what it did.
What kind of integration this is
GitHub is an app connection: agents that Ando runs use it through tools, within the access the connected account allows. GitHub events can also be routed into a conversation as signed webhooks through the Ando API.
Can an agent merge a pull request that needs review?
Not by skipping the review. A GitHub connection does not bypass branch protection or required pull request reviews. The agent works within the permissions of the connected account.
Can we limit which repositories agents see?
Yes. You choose repositories when you install the GitHub App, and the connection in Ando can be limited to selected repositories as well.