Brainboard's documentation
Website 🏛️Go to the app ↗
  • Welcome
  • Getting started
    • Fast track
    • Start with a template
    • Start with AI
    • Use cases videos
    • Brainboard philosophy
  • Cloud design
    • Left bar
      • Cloud resources
      • Input & output
    • Design area
      • Node
      • ID card
      • Connectors
      • Versioning
      • Graphical options
    • One action
    • Code Edition
  • Data
    • Data structure
      • Project
      • Environment
      • Cloud architecture
        • Terraform files
        • Readme file
        • Architecture Synchronization
        • Remote backend
      • Template
    • Cloud providers
      • Supported cloud providers
      • Customize provider configuration
      • Unsupported cloud providers
    • Terraform / OpenTofu
      • Modules
        • Module
        • Import modules
        • Manage module
        • Terraform registry credentials
        • Use modules
    • Disaster recovery
  • Automation
    • CI/CD engine
    • Supported plugins
      • Terraform
      • Security
        • Trivy
        • Tfsec
        • Terrascan
        • OPA
        • Checkov
      • Infracost
      • Notifications
        • Email
        • Slack
        • Microsoft Teams
      • Webhooks
    • Pipelines
    • Workflow templates
    • Drift detection
      • Types of drift
      • Remediation
    • Self-Hosted Runner
      • Deploy runner with Kubernetes
      • Deploy runner with docker-compose
  • Settings
    • Overview
    • Authentication
      • Login into Brainboard
      • Single sign-on (SSO)
    • Account management
    • Organization
    • Members
    • Teams
    • Roles & Permissions (RBAC)
      • Level of access
      • Organization RBAC
      • Project RBAC
    • Integrations
      • Git configuration
        • GitHub
        • Azure DevOps (ADO)
        • Bitbucket
        • GitLab
        • How to use
      • Cloud providers
        • AWS
        • Azure
        • GCP
        • OCI
  • Security
    • Data managed by Brainboard
    • SOC 2 Type II
    • Role Based Access Control
  • Help & FAQ
    • Shortcuts
    • FAQ
    • Migration
      • Import from AWS
    • Support
    • Glossary
  • Changelog
Powered by GitBook
On this page
  • Description
  • Types of connections
  • Supported Git providers

Was this helpful?

Edit on GitHub
  1. Settings
  2. Integrations

Git configuration

PreviousIntegrationsNextGitHub

Last updated 1 month ago

Was this helpful?

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.

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.

  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

  2. GitLab

  3. Bitbucket

  4. Azure DevOps (ADO)

When doing Pull Requests, Brainboard sends the information on behalf of the user creating the PR to be able to track who does what. Refer to page for more information about how it works. For now only GitHub has an app integration.

Pull Requests