Skip to main content
Git Sync automatically creates a Pull Request (GitHub) or Merge Request (GitLab) in your repository whenever you merge branches or commit to the main branch in BRMS. This keeps your Git repository in sync with your decision files.

​
Prerequisites

Before enabling Git Sync on a project, an organization administrator must connect a Git provider. For self-hosted deployments, the provider must first be configured at the server level — see Git integrations.

​
Connect a Git provider

Organization administrators can connect GitHub or GitLab from the integrations page.
  1. Navigate to Admin > Integrations
  2. Find the card for your preferred provider (GitHub or GitLab)
  3. Click Connect

​
Connecting GitHub

  1. Click Connect to GitHub
  2. If the GitHub App is already installed on your account, select which organization to connect
  3. If not installed, you’ll be redirected to install the GitHub App — choose which repositories to grant access to
  4. Complete the authorization

​
Connecting GitLab

  1. Fill in the connection form:
  1. Click Connect to GitLab
  2. Authorize the application in GitLab
  3. You’ll be redirected back to BRMS
GitLab credentials are encrypted and stored securely using your organization’s secrets provider. For self-hosted deployments, secrets management must be configured before connecting GitLab.

​
Enable Git Sync on a project

Once a Git provider is connected, project managers can enable Git Sync for individual projects.
  1. Navigate to Project Settings > Git Sync
  2. Toggle Enable Git Sync to on
  3. Configure the sync settings:
  1. Click Save Configuration
You must specify a subdirectory path. Syncing to the repository root is not allowed.

​
How Git Sync works

When you merge a branch in BRMS:
  1. A new branch is created in the Git repository (e.g., commit-abc12345)
  2. All decision files from your project are committed to the configured path
  3. A metadata file is included with sync information
  4. A Pull Request or Merge Request is automatically created against your target branch

​
Synced file structure

​
Project metadata

Each sync includes a .config/project.json file with metadata:

​
Sync status

After a merge, the commit history shows a sync status badge:

​
Permissions

​
Troubleshooting

​
”No Git integration configured” warning

No Git provider is connected to your organization. Contact your organization administrator to configure a GitHub or GitLab integration in Admin > Integrations.

​
Sync status shows “Failed”

Hover over the red badge to see the error message. Common causes:
  • Repository access was revoked
  • Target branch no longer exists
  • Network connectivity issues

​
Sync stays “Pending” for more than 5 minutes

If a sync shows “Pending” for an extended period, it may have failed silently. The status will eventually change to “Sync timed out”. Check your Git provider to see if a PR was partially created.

​
Cannot see repositories in dropdown

The connected Git provider account may not have access to the repository you’re looking for. For GitHub, verify the GitHub App is installed on the organization that owns the repository. For GitLab, verify the connected user has access to the repository.