Docs
Schedule demo Open app

Connecting Git repositories

Eraser supports connecting repositories from GitHub, GitLab, and Azure DevOps (Bitbucket coming soon). By connecting your Git repositories, you can:

  • Use your codebase as context to automatically generate AI diagrams (e.g. “draw an architecture diagram of our aws/staging/ environment”)
  • Set up Eraserbot to monitor and keep important diagrams synced with your code
  • Commit .md and .eraserdiagram files directly to your repository from Eraser

Codebase diagrams work with every supported platform. Eraserbot monitors are available for GitHub and GitLab, and committing files back to your repository (Git sync) is available for GitHub.

To get started, connect your organization from your preferred Git platform.

Connecting GitHub repositories

  1. Go to Settings > Git Connect
  1. Click Connect new git org > GitHub
  2. Log in to your GitHub account, select the organization you’d like to connect, and install the Eraser GitHub App. Choose which repositories to authorize and click Install & Authorize.
  1. Your authorized repositories will appear on the Git Connect page in Eraser.

Connecting GitLab repositories

  1. Go to Settings > Git Connect
  1. Click Connect new git org > GitLab
  2. Create a GitLab access token with api scope and paste it on this page. You can use a personal, group, or project access token.
  1. Select the GitLab projects you’d like to connect to Eraser.
  1. Your connected projects will appear in the Git Connect page in Eraser.

Connecting Azure DevOps repositories

  1. Go to Settings > Git Connect
  2. Click Connect new git org > Azure DevOps
  3. Enter your Azure DevOps organization name — the part after dev.azure.com/ in your repository URLs.
  4. Create an Azure DevOps personal access token with Code (Read) and Project and Team (Read) scopes, and paste it on this page. Scope the token to your organization rather than All accessible organizations — Microsoft is retiring multi-organization tokens on December 1, 2026.
  5. Select the repositories you’d like to connect to Eraser. Repositories are listed as project/repository, because Azure DevOps repository names are only unique within a project.
  6. Your connected repositories will appear on the Git Connect page in Eraser.

Because the token belongs to the user who created it, we recommend creating it under a service account so access doesn’t break when someone leaves the team. Note that Azure DevOps deactivates a token if its owner doesn’t sign in periodically, so the service account needs an occasional interactive sign-in.

Azure DevOps Server (on-premises)

To connect a self-hosted Azure DevOps Server instance, check Use an on-prem Azure DevOps Server and enter your server URL — including any path prefix, for example https://azuredevops.example.com/tfs — along with your project collection name, usually DefaultCollection. Your server must be reachable from Eraser.

What’s supported

Azure DevOps repositories can be used as context for codebase diagrams and AI chat. Git sync and Eraserbot monitors are not currently available for Azure DevOps.

Managing Git repositories

For each connected repository, you can configure one of the following access levels:

  • Active: Eraser can access this repository to generate codebase diagrams and enable Eraserbot monitors.
  • Active and synced (GitHub only): In addition to all the Active capabilities, Eraser can also commit .md files and .eraserdiagram files to the repository and pull them back in.
  • Inactive: Eraser has no access to this repository.