Set up your Git release detection method
LinearB uses 3 different methods to detect releases of code. By default LinearB regards tags as the indication of code released. In order to customize how LinearB detects your Git releases go to Company Settings and select the Advanced tab.
Without any additional configuration every commit that appears in a tagged branch will be considered as code that was released. If tags are used for other purposes as well, you can set up a regular expression that indicates prefix/suffix of tag names that are used for releases. In this case only the tags that match the specified regular expression will be considered as releases.
PRs to a Dedicated Branch
If your organization uses a dedicated branch or set of branches for releases and open a PR when merging, select the option to "Detect my releases by Pull Requests to a dedicated branch" to enable this detection method.
In this case every PR that is merged to a dedicated release branch is considered as released. In order to use this method, specify a regular expression that matches the branch/es used for releases. (By default the "release" branch is master)
Merges to a Dedicated Branch
The third method for detecting releases is for organizations that use a dedicated branch/es for releases, select "Detect my releases by direct merged to a dedicated branch" to enable this detection method.
In this case every branch that is merged to your dedicated release branch is considered as released. Specify a regular expression that matches the branch/es used for releases. (By default the "release" branch is master)
Multi-Stage Release Detection (API)
Multi-stage release detection is available using LinearB's Release API. This feature is available to enterprise plans, please contact your LinearB CSM to implement the release API