GitHub

The GitHub integration connects your code repositories to Sprigr Teams. Agents can browse repositories, read code, search issues and pull requests, manage branches, and review commits. This is particularly useful for development teams that want agents to assist with code reviews, issue triage, or project status updates.

Prerequisites

A GitHub account with access to the repositories you want your agents to use.
A Personal Access Token (PAT) with the appropriate scopes. You will generate this in GitHub’s settings.
Admin or Owner role in your Sprigr Teams organisation.

Connecting GitHub

Generate a Personal Access Token

In GitHub, go to Settings > Developer settings > Personal access tokens > Fine-grained tokens. Click Generate new token.

Give the token a descriptive name (for example, “Sprigr Teams Integration”) and select the repositories you want to grant access to. At minimum, enable the following permissions:
- Repository access — Select specific repositories or all repositories
- Contents — Read access (to browse code and files)
- Issues — Read and write access (to list, create, and comment on issues)
- Pull requests — Read and write access (to list and review PRs)
- Metadata — Read access (required for all tokens)
Click Generate token and copy the token immediately — you will not be able to see it again.
Open the Integration Hub

Sign in to team.sprigr.com and click Integrations in the sidebar.
Find GitHub

Locate the GitHub card and click Connect.
Enter your token

Paste the Personal Access Token you generated in Step 1. Click Save to complete the connection.
Verify the connection

The GitHub card will show a green “Connected” badge. You can test the connection by asking an agent with the GitHub integration to list your repositories.

Available tools

Tool	Action	Description
`github`	`list_repos`	List repositories accessible to the connected account
`github`	`get_repo`	Get details about a specific repository
`github`	`list_issues`	List issues in a repository, with optional filters (state, labels, assignee)
`github`	`create_issue`	Create a new issue with a title, body, labels, and assignees
`github`	`list_pull_requests`	List pull requests in a repository
`github`	`read_file`	Read the contents of a file from a repository
`github`	`list_branches`	List branches in a repository
`github`	`list_commits`	List recent commits on a branch
`github`	`create_comment`	Add a comment to an issue or pull request

Common use cases

Issue triage — An agent reviews new issues, adds labels based on content, assigns them to the appropriate team member, and leaves a comment acknowledging the report.
PR summaries — Ask an agent to summarise the changes in a pull request, including what files were modified and what the commit messages say. Helpful for managers who want a quick overview.
Status reports — A workflow step queries GitHub for open issues and recent merged PRs, then generates a weekly development status report.
Code reference — During a conversation about a bug, an agent reads the relevant source file from the repository to help troubleshoot the issue.

Troubleshooting

“Bad credentials” error Your Personal Access Token may have expired or been revoked. Generate a new token in GitHub and update the integration in the Hub.

Agent cannot see a repository The token must have access to the specific repository. If you used a fine-grained token scoped to certain repositories, make sure the repository in question is included.

“Rate limit exceeded” error GitHub enforces API rate limits. If agents are making many requests in a short period, they may hit the limit. Consider reducing the frequency of automated queries or using a token from a GitHub account with higher rate limits.

Next steps

Integrations Overview — See all available integrations.
Agent Settings — Assign the GitHub integration to specific agents.
Workflows — Use GitHub actions as steps in automated workflows (e.g., create an issue when a workflow detects a problem).