All Categories ​>​ ​Understanding LinearB Metrics

Understanding LinearB Metrics

Draft Pull Requests

Draft/WIP Pull Requests. Currently Draft PRs are supported in GitHub and GitLab. Azure repos does not currently report via their API the date-time of when a PR made live and BitBucket does not have t…

Updated by Betsy Rogers

How does LinearB handle squash merges?

What is Git Squash? Git squash is a feature that allows developers to merge multiple sequential commits. The process involves choosing a base commit and merging all the changes from the sequential co…

Updated by Betsy Rogers

How is Cycle Time Calculated?

How is Cycle Time Calculated. Cycle time calculates the average time it takes for engineering tasks to go through the different phases of the software delivery process, from the first code commit to…

Updated by Betsy Rogers

Indirect Code Contribution 👻

Indirect Code Contribution. Looking at the commits and code that is part of a branch, we distinguish between 2 types of contribution to the branch. Direct contribution - direct commits to the branch.…

Updated by Betsy Rogers

Understanding Code Changes

Understanding Code Changes. General. Code changes is a metric that measures the changes that are done in the code base over time. It includes either new code or refactored code and is counted in a nu…

Updated

Understanding Releases

Understanding Releases. LinearB is detecting releases and following the release count in several metrics (Deployments, Deploy Frequency). Releases are counted on the repository level and counted base…

Updated

What are LinearB Burnout Indicators?

Avoid burnout and cognitive overload by monitoring and balancing your team's workload.

Updated by Betsy Rogers

Work Breakdown Terms

Work Breakdown Terms. Refactor - Changes to legacy code. LinearB considers code "legacy" if it has been in your code-base for over 21 days. Rework - Code that is rewritten or deleted shortly after be…

Updated by Ariel Illouz

Powered by HelpDocs (opens in a new tab)