Team Activity

Git Activity

The Git Activity section provides visibility into engineering collaboration and development efficiency through repository-level events such as pull requests, commits, and code reviews. Below are the definitions, calculations, and use cases for each Git activity metric tracked.

1. PRs Created

  • Definition: Total number of pull requests created by the member within the selected period.
  • Calculation: Count of PRs authored in the connected Git repositories.
  • Use Case: Indicates individual contribution volume. A high number may reflect active feature development or participation in team workflows.

2. Commits Count

  • Definition: Number of commits pushed by the user to the repository.
  • Calculation: Count of Git commits linked to the user’s account.
  • Use Case: Useful for gauging raw development activity. Can help validate consistency in code delivery.

3. Avg Member Time to Merge

  • Definition: Average time from when a pull request is opened to when it is merged.
  • Calculation: (Merge Date – PR Creation Date), averaged across all merged PRs.
  • Use Case: Helps identify delays in code integration. Long times may signal bottlenecks in review or merging processes.

4. Avg Member Time to First Approval

  • Definition: Average time from when a PR is opened to when it receives the first approval.
  • Calculation: (First Approval Date – PR Creation Date), averaged across all approved PRs.
  • Use Case: Useful for tracking review responsiveness. Delays may indicate process issues or limited reviewer availability.

5. Reviews Count

  • Definition: Total number of PR reviews submitted by the member.
  • Calculation: Count of distinct review submissions (approve, comment, or request changes).
  • Use Case: Measures collaboration. High review counts reflect engagement in peer quality control and team support.

6. PR Comments Count

  • Definition: Number of comments a user made on others’ pull requests.
  • Calculation: Total comment entries made on PRs.
  • Use Case: Encourages feedback culture. Active commenting can help surface technical debt, bugs, or alternative solutions.

7. Avg Member Review Time

  • Definition: Average time taken by the member to respond to PRs assigned for review.
  • Calculation: (Time of First Review – Time PR Was Assigned or Opened), averaged across reviewed PRs.
  • Use Case: A key signal for code review efficiency. Long durations may lead to slower delivery cycles.

These Git activity metrics complement task-level performance by offering insights into how engineers collaborate in code. Tracking them helps organizations identify high performers, detect review bottlenecks, and improve continuous delivery practices.

Powered By EazyDocs