Skip to main content

​
GitHub Integration

Connect GitHub to enable the AI agent to access code context, pull requests, and deployment information during investigations.

​
Capabilities

Once connected, the AI agent can:
CapabilityDescription
Browse CodeView repository files and code
Search CodeSearch across repositories
Pull RequestsReview recent PRs and changes
CommitsView commit history and diffs
DeploymentsCheck deployment status
ActionsReview workflow runs

​
Prerequisites

  • A GitHub account or organization
  • A Personal Access Token (PAT) or GitHub App
  • Read access to the repositories you want to query

​
Setup

1

Create a Personal Access Token

  1. Go to GitHub Settings → Developer settings → Personal access tokens → Fine-grained tokens
  2. Click Generate new token
  3. Set an expiration date
  4. Select the repositories to grant access
  5. Set permissions (see below)
  6. Generate and copy the token
2

Add Integration in AccelOS

  1. Go to Integrations in AccelOS
  2. Click GitHub
  3. Enter a name (e.g., “Production GitHub”)
3

Configure Credentials

Enter the following:
  • Token: Your GitHub Personal Access Token
  • Organization (optional): Limit to a specific org
4

Test and Save

Click Test Connection to verify, then Save.

​
Required Permissions

For fine-grained tokens, grant these permissions:
PermissionAccess LevelWhy It’s Needed
ContentsReadView repository files
MetadataReadAccess repository information
Pull requestsReadView PR details
Commit statusesReadCheck CI/CD status
ActionsReadView workflow runs
DeploymentsReadCheck deployment status
Use fine-grained tokens when possible - they provide more granular control than classic tokens.

​
GitHub Enterprise

For GitHub Enterprise Server, provide the API URL: 
https://github.your-company.com/api/v3

​
Example Queries

Once connected, you can ask the AI agent: 
What changed in the last deployment to production?

Show me recent commits to the payment service

Were there any PRs merged today that touched the database code?

What's the status of the CI pipeline?

​
Troubleshooting

  • Verify the token is correct and hasn’t expired
  • Check that the token has access to the requested repositories
  • For fine-grained tokens, ensure the correct organization is selected
  • Verify the repository exists and the token has access
  • Check the organization/owner name is correct
  • Ensure the repository isn’t private without proper token access
  • GitHub has API rate limits (5,000 requests/hour for authenticated requests)
  • Consider using a GitHub App for higher limits
  • Wait for the rate limit to reset