What this section is for
See how many pull requests have merged, how long they took, who committed code and which changes received reviews. Choose a team, dates and repository. Filters stay in the URL and carry over to Delivery and Profiles. The calculated activity index is shown separately with an explanation of its limits.
When to use
- Before a team meeting, to check recent code changes.
- After a release or incident, to check activity for the relevant dates.
- When you need an overview before looking at individual repositories or developers.
Quick start
- 1Choose a team, start and end dates, and repository. Both dates are included. Enter an exact author email to view one person.
- 2Read the four metric cards and the note explaining which pull requests are counted.
- 3Switch from the chart to the table for daily totals, or download them as CSV.
- 4Open Delivery for pull request details, Profiles for individual developers or Knowledge Map for commit distribution.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Date range | Sets the dates included in the team overview. | Start with the last 30 days. Choose 90 or 180 days to look at changes over several months. | Comparing totals from periods of different lengths without accounting for the difference. |
| Team | Decides whose commits and pull requests are aggregated. | Check the selected team before sharing numbers: the app remembers your previous choice. | Sharing another team’s results without checking the filter. |
Usage example
Scenario: Time to merge is increasing.
- 1Choose the dates and repository where merge time increased.
- 2Open Delivery; the filters carry over.
- 3Compare pull request counts and average merge time with a previous period of the same length. Check individual changes and discuss the delays with the team.
What this shows: You know when and where merge time increased and can show the team specific changes to investigate.
FAQ
Why are some cards empty?
The app distinguishes between a missing connection, a loading error and no activity for the selected dates. Check the last sync and your filters. An empty card does not always mean zero activity.
What does bus factor mean here?
The smallest number of authors responsible for at least half the commits in the selected history. A bus factor of 1 means one author made at least half the commits. It does not establish who knows the system or owns the code.
How can I share the data with these filters?
Copy the URL. The recipient needs access to the same team and repositories; access restrictions can change what they see.
Tips
- Use periods of the same length and the same team when comparing results.
- Record the team and dates when you share a screenshot or copy a value.