Skip to main content
Table of Contents

Configuring Release Detection in LinearB

Configure code release detection methods.

Steven Silverstone
Updated by Steven Silverstone

Overview

LinearB provides four methods for detecting code releases. By default, LinearB considers tags as release indicators. Release detection can be configured at both the global level and on individual repositories.

By default, all repositories in a LinearB instance inherit the global release detection method.

If a repository has a customized release detection method, it will use only that method. It will not use both global and repository-specific settings, and it will not revert to the global configuration.
Release Detection Methods

1. Tags (Default Method)

By default, every commit that appears in a tagged branch is considered released.

  • If your organization uses tags for multiple purposes, you can configure a regular expression (regex) to filter tag names by prefix or suffix so that only relevant tags are treated as release indicators.

2. Pull Requests to a Dedicated Branch (Default Alternative)

This method causes the Deploy Time metric to register as 0.

By default, LinearB listens for pull requests merged into branches that match: ^(main|master|production|prod)$

  • If your organization uses dedicated branches for releases and merges changes via pull requests, enable:
    “Detect releases by Pull Requests to a dedicated branch.”
  • Every pull request merged into the release branch is considered a release event.
  • You can customize the branch pattern using a regex filter to match your organization’s naming conventions. (By default, this is set to “master.”)

3. Merges to a Dedicated Branch

This method is intended for organizations that merge directly into dedicated release branches without using pull requests.

  • Enable:
    “Detect releases by direct merges to a dedicated branch.”
  • Any branch merged into the release branch is considered released at the time of the merge.
  • Specify a regex pattern to match the relevant release branches. (By default, this is set to “master.”)

4. Deployment API (Multi-Stage Release Support)

For organizations that rely on CI/CD pipelines for release management, LinearB supports release detection via the Deployment API.

  • Your CI/CD system can trigger release events using the LinearB Deployment API .
  • Supports multi-stage release detection to track different deployment stages.
  • Available on Enterprise plans. Contact your LinearB account manager for implementation assistance.
Global vs. Repository-Specific Release Detection

Global Release Detection

To configure release detection globally for all repositories:

  1. Navigate to Settings → Company Settings → Advanced.
  2. In the Release Detection section, choose the method LinearB will use to identify and track releases.
  3. Click Save to apply the changes.

Repository-Specific Release Detection

To configure a custom release detection method for a specific repository:

  1. Navigate to Settings → Company Settings → Git.
  2. Select the required repository.
  3. Click the Settings icon (⚙) next to the repository.
  4. Select the required release detection method.
  5. Click Save to apply the changes.

How did we do?

Configuring Auto-Monitoring for Git Repositories

Git Activity: Metrics & Filters Glossary

Contact