Skip to main content

​
Overview

Git Settings let your organization control how Backline opens pull requests with fixes, so they follow your team’s conventions and policies. The settings apply to every pull request Backline opens in your connected repositories. Pull requests that are already open are not affected when you change a setting. You can find this page under: Settings → Git settings

​
Pull Request

PR Title Prefix

Text added to the start of every pull request title Backline opens, for example [SEC] {ticket_id}. Use {ticket_id} to insert the linked ticket’s ID. Up to 50 characters.

Labels

Labels added automatically when the pull request is opened, for example dependencies. Leave empty to apply no labels.

​
Branches

Branch Prefix

Text added to the start of every branch name Backline creates, for example fix/{ticket_id}/. Use {ticket_id} to insert the linked ticket’s ID. Up to 50 characters.

Base Branch

The branch pull requests are opened into, for example main. If empty, each repository’s default branch is used.

Source Branch

The branch the fix branch is created from, for example develop. If empty, the base branch is used.

Commit Prefix

Text added to the start of each commit subject line, for example fix: or [Backline]. Up to 50 characters.

​
Auto-Rebase Pull Requests

When turned on, Backline keeps its pull requests up to date by rebasing them on the base branch when it changes.

​
Reviewers

Assign Code Owners as PR Reviewer

Automatically requests a review from the code owners of the changed files.

Maximum Number of Reviewers

The most reviewers that can be assigned to a pull request, from 1 to 5. Available only when Assign code owners as PR reviewer is turned on.

​
Default Values

Leave a field empty to use Backline’s default for it. For example, an empty Base branch uses each repository’s default branch. Click Reset to default to return every setting on the page to Backline’s defaults. The button is disabled when all settings already match the defaults.

​
Saving Changes

After changing the settings, click Save changes to apply them. You can click Cancel to discard your changes and restore the last saved settings. If you leave the page with unsaved changes, Backline asks whether to save or discard them.
Editing Git Settings requires write permission for settings. Users without it can view the page but cannot change it.