Review Developer Activity in Azure DevOps

Begin with the question

Useful questions include “when did this repository change?”, “which branch was active before the release?”, and “where should I inspect a suspected regression?” Avoid asking a commit chart to judge individual performance.

Use a layered review

1. Scan the calendar for active and quiet periods.
2. Filter by repository, branch, or contributor.
3. Open the commits for the relevant date.
4. Follow associated pull requests, reviews, work items, and deployments.

Account for missing context

Squash merges, rebases, paired work, code review, design, incident response, and work in other systems all affect what a commit graph shows. Treat activity as a route into the history, not a ranking.