LinearB is detecting releases and following the release count in several metrics (Deployments, Deploy Frequency). Releases are counted on the repository level and counted based on the release detection strategy configured by the customer. (Learn more about release detection strategies)
A branch/PR considered released if it meets the criteria of the release detection strategy. In case you are using tags as your release strategy, all the branches in the repository that are tagged with the same tag will be a part of the release defined by this tag. In case you are using a strategy based on merging each branch that is merged will be considered as a release.
Releases are attributed to the branch contributors. If there is a contributor that committed to a branch that was released this contributor will be attributed with the release. If more than one contributor committed to the same branch, the release will be counted for each one of the contributors.
So for example, If you are using tag strategy and someone contributed to 4 different branches (in the same repository) that were tagged with the same tag, this individual will be attributed with 1 release.
If you are using one of the mergings strategies, and this individual was a contributor in 3 branches that were eventually merged into the release branch, this individual will be attributed with 3 releases.
Team level release attribution
Release (regardless of the release detection strategy) is attributed to a specific team in case it was attributed to one of the team members. However, if the same release is attributed to 2 contributors that are in the same team, only one release will be counted for the team.
If a contributor is a member of more than one team, the release will be attributed to each one of the teams this individulals this member is a part of.