# Git configuration

### Description

This settings page allows you to configure access to your Git repositories to be able to either push the code to them or pull the code if you are migrating to Brainboard.

<figure><img src="/files/cMkcQQoczpBFgGwacz3y" alt=""><figcaption></figcaption></figure>

### Types of connections

There are 3 types of Git connections:

1. Git app integrations: is a mechanism that allows you to control access to repositories and users from your git provider and not inside Brainboard.

   Which means that with this integration, users don't use their personal git tokens.

   When doing Pull Requests, Brainboard sends the information on behalf of the user creating the PR to be able to track who does what.

   For now only GitHub has an app integration.
2. Organization connections: You can configure access to your Git repository in a way that any user inside your organization can use it. It may be helpful if you don't want your users to manage Git connections, so they can see all projects and do pull requests to any one of them.
3. Personal connections: Git personal tokens are used by every user individually. So the users will be able to see only project and repositories they have access to and they do pull requests, you can identify exactly who did it.

### Supported Git providers

Brainboard supports the following Git providers:

1. [GitHub](/settings/integrations/git-configuration/github.md)
2. [Azure DevOps (ADO)](/settings/integrations/git-configuration/ado.md)
3. [GitLab](/settings/integrations/git-configuration/gitlab.md)
4. [Bitbucket](/settings/integrations/git-configuration/bitbucket.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.brainboard.co/settings/integrations/git-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.