← All features
Primary measure

Lead with merged PRs, or with commits. Your call.

Some teams review everything before it ships. Others push commits straight to main. Pick your team’s primary measure and the dashboard, the Who ships ranking, the digest and the reports follow. Both stay tracked.

Settings · Primary measureper team · changeable any time
PRMerged pull requestsWe review everything before it ships.KPIs: Merged PRs · 1st review · Pending
CCommitsWe push often, PRs are rare.KPIs: Commit effort · Commits · Commits/day
1One toggle per teamSet it when you create the team or later in Settings › General. Takes effect immediately.
2Everything followsKPI order, Who ships, member sort, report sections and the Monday digest switch together.
3Nothing is lostBoth metrics are always collected. The other one stays one click away.
Mixed teamsA workspace can have PR-first and commit-first teams side by side.
HistorySwitching does not rewrite history; past reports keep the measure they were generated with.
DefaultNew teams start with merged PRs. Commit-first is one click.

Teams work differently, tools pretend they do not

A platform team reviews everything: branches, pull requests, two approvals, squash merge. A small product team pushes to main several times a day and reviews after the fact. Most engineering analytics tools assume the first model and show empty dashboards to the second.

Squadlog asks one question per team: what comes first, merged PRs or commits? The answer orders the KPI cards, picks the metric behind Who ships, sorts the members table, and writes the Monday digest and reports around that measure.

What changes, what does not

With merged PRs first, the dashboard leads with merged PRs and time to first review; the ranking counts merges. With commits first, it leads with commit effort and commits; the ranking sums effort scores. In both cases every event is still collected, so switching later does not lose history, and the alerts on PRs still run if the team opens any.

Changing the measure

The setting lives in the team’s General settings and can be changed at any time by a manager. Reports already generated keep the measure they were generated with, so a past document does not change under your feet.

Who it is for

For teams that were told their workflow was wrong

Trunk-based teamsDashboards that are not emptyCommits first: effort, commits and a ranking that reflects what landed on main.
Review-heavy teamsReview flow at the topMerged PRs first: time to first review and stuck PRs lead the page.
Organizations with bothOne setting per teamEach team picks its own; the CTO sees each one in the terms that fit it.
Questions

About primary measure

All answers →
  • Yes, any time, from the team settings. History is kept; only the ordering and the ranking metric change.
Other features