Understanding Releases

Releases are tracked at the repository level and are defined based on the release detection strategy configured by the customer. Learn more about release detection strategies)

What Qualifies as a Release?

A branch or pull request (PR) is considered released if it meets the criteria defined in the configured release detection strategy:

• Tag-Based Strategy: When tags are used as the release strategy, all branches in the repository associated with the same tag are considered part of the release defined by that tag.
• Merge-Based Strategy: When merging is used as the release strategy, each branch merged into the main branch is considered a release.

Release Attribution

Contributor-Level Attribution

Releases are attributed to the contributors of the branch involved in the release:

• If a contributor commits to a branch that is later released, they are credited for the release.
• If multiple contributors commit to the same branch, the release is counted for all contributors.

Examples:

• Tag-Based Strategy: If a contributor works on 4 different branches within the same repository, and all are tagged with the same release tag, they are credited with 1 release.
• Merge-Based Strategy: If a contributor contributes to 3 branches that are eventually merged into the release branch, they are credited with 3 releases.

Team-Level Release Attribution

Releases are attributed to a team if any of its members contributed to the release. However:

• If a release is attributed to multiple contributors within the same team, it is counted as 1 release for the team.
• If a contributor belongs to more than one team, the release is counted for all the teams they are a part of.

This approach ensures accurate tracking of releases at both the individual and team levels while avoiding duplicate counts for the same release.

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.