Score Settings

Overview

Score settings control when GitVelocity analyzes pull requests and how results are shared. These options are configured per repository on the repository settings page under PR Review Settings.

Pause Scoring

Toggle Pause Scoring to temporarily stop all scoring for a repository. No PRs will be analyzed while scoring is paused, regardless of other settings.

This is useful during large migrations, repository restructuring, or any period where scoring results wouldn't be meaningful. Re-enable scoring when you're ready, and any PRs that merged while paused will not be retroactively scored.

Score on PR Open

Enable Score on PR Open to trigger scoring when a pull request is opened, not just when it merges. This gives the team early visibility into PR complexity before the code lands.

When enabled, the score updates automatically if the PR changes before merge. The final score is always based on the merged diff.

Score on Merge

Score on Merge is the default scoring trigger. PRs are scored when they merge to the default branch. This is the most common configuration and ensures scores reflect the final state of the code.

You can enable both Score on PR Open and Score on Merge simultaneously to get early feedback and a final score.

Post Scores to GitHub

Enable Post Scores to GitHub to automatically post the velocity score as a comment on the pull request in GitHub. This lets the team see scores without leaving GitHub.

The comment includes the overall score, dimension breakdown, and a link to the full analysis in GitVelocity.

Show Code Review

Enable Show Code Review to display an AI-generated code review alongside the numeric score. The review provides detailed, line-level feedback on the PR beyond the score itself.

This is particularly useful for teams that want to use GitVelocity as a supplementary code review tool in addition to velocity measurement.