GitHub Enterprise Server Integration

Documentation Index

Fetch the complete documentation index at: https://docs.devin.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

1. GitHub App (Recommended) — Register and install a dedicated GitHub App on your GHES or GHEC instance. This provides a streamlined setup experience and does not require managing personal access tokens.
2. Personal Access Token (PAT) — Create a service account and generate a fine-grained personal access token. This method works for all GHES versions.

​

GitHub App Setup

1. App Registration — Register a GitHub App on your GHES or GHEC instance. You only need one App registration per instance.
2. App Configuration — Configure the registered App on your GHES or GHEC instance (e.g., make it public and opt out of token expiration).
3. App Installation — Install the registered App on each GitHub organization you want Devin to access. You need one installation per organization.

​

Prerequisites

• A Devin user with Manage git permissions
• Owner or admin access to the GitHub organization where the App will be registered

​

Step 1: Register the GitHub App

1. In your Devin account, navigate to Enterprise Settings → Integrations → GitHub.
2. Expand the Advanced section to reveal the GitHub Enterprise options.

3. Click Register App.
4. In the modal that appears, enter the hostname of your GHES or GHEC instance and the organization where the App will be registered.

5. You will be redirected to GitHub. Click Register App to complete the registration.

6. After being redirected back to Devin, the GitHub App is now registered in your GitHub organization.

​

Step 2: Configure the GitHub App

1. On your GHES or GHEC instance, navigate to the GitHub organization specified during registration.
2. Go to Settings → Developer Settings → GitHub Apps and select the Devin App.

3. In the Advanced section, under Danger zone, click Make public. This allows the App to be installed across other organizations on the same instance.
4. Navigate to the Optional features section and opt out of User-to-server token expiration. This prevents access tokens from expiring and avoids the need for users to re-authorize the App periodically.

​

Step 3: Install the GitHub App

1. In your Devin account, navigate to Enterprise Settings → Integrations → GitHub.
2. Expand the Advanced section and click Install App.
3. In the modal, select the GitHub App registered under your GHES or GHEC instance.

4. You will be redirected to GitHub, where you can choose a GitHub organization and select which repositories to grant Devin access to. We recommend granting access to all repositories.
5. After completing the installation, you will be redirected back to Devin. A new git connection will appear in Settings → Integrations → GitHub.

​

Troubleshooting

​

Personal Access Token Setup

​

Create a Service Account for Devin

1. Within your GitHub Enterprise, create a new GitHub account for Devin to use. This is important to ensure all of Devin’s access and usage can be properly tracked and managed.
2. Add the newly created service account to all relevant GitHub organizations as a Member. Verify that the account has access to all of the repositories that Devin is expected to access.

​

Generate a Personal Access Token for Devin

1. While logged into the service account, click on the profile picture in the upper-right corner, then click Settings.
2. In the left sidebar, click Developer settings.
3. In the left sidebar, under Personal access tokens, click Fine-grained tokens.
4. Click Generate new token.
5. Add the Token name and Expiration.
   Note: When the token expires, Devin will immediately lose all access to GitHub and a new token will need to be created.
6. Under Resource owner, select the correct organization.

7. Under Repository access, select which repositories you want Devin to work with. Tokens always include read-only access to all public repositories on GitHub.
8. Make sure the token has the following permissions which are required for Devin to work properly:

9. Click Generate Token and save the token that is displayed.
   Note: Admin approval may be needed depending on your GitHub settings.
10. To validate that the token has all the necessary access and permissions, create and push a test branch on your local machine to a repository in the organization.
11. Once the token has been generated and tested, reach out to your Cognition point of contact to finish the setup process. If you are not currently working directly with our team, reach out to enterprise@cognition.ai.

​

Validating PAT Permissions Locally

# Authenticate with gh CLI using your token
export GH_TOKEN=your_personal_access_token
export GH_HOST=your-github-enterprise-server.com

# Clone the repository
gh repo clone your-organization/your-repository
cd your-repository

# Create a test branch
git checkout -b test-devin-token-$(date +%s)

# Make a small change
echo "# Test" >> TEST.md
git add TEST.md
git commit -m "Test: Validate Devin token permissions"

# Push the branch (tests contents write permission)
git push origin HEAD

# Create a pull request (tests pull requests write permission)
gh pr create --title "Test: Validate Devin token permissions" \
  --body "This is a test PR to validate token permissions." \
  --base main

# Clean up: close the test PR and delete the test branch
gh pr close pr-number --delete-branch

​

Using Devin with the GitHub Integration

​

Security Considerations

• We recommend enabling branch protections on master to ensure checks are enforced before Devin can merge any changes.
• If Devin is connected to your organization’s GitHub account then it will have the same permissions for any user with access to the GitHub and Devin organizations.
• Devin will not mirror the permissions of the user running a session with Devin, it will retain the permissions granted at the org-level.
• Devin cannot create new repos in your GitHub account.