We've rolled out an update to ensure that your Time to Develop metric more accurately reflects the active development time for the work being shipped. It provides a cleaner signal by removing the noise from routine branch management and code integration tasks.

Our refined algorithm filters out unrelated commits from actions like changing a base branch or merging in hotfixes. Each commit is now only associated with a single pull request and will be excluded from the calculation if it meets any of the following conditions:

1. It was already part of a merged PR. This filters out standard merge commits and commits from other branches (e.g. a hotfix) that were merged into the feature branch before the PR was completed.
2. It results from a base branch change. We ignore commits that are temporarily added to a PR's history when its base branch is changed, ensuring only commits relevant to the final base branch are included.
3. The author and committer are different. This excludes commits that were authored by another developer and introduced into the branch history through actions like cherry-picking.

These changes are detailed in our documentation. If you have any questions, please reach out to us at support@software.com.