- Pull Requests: Analyzes pull request metrics and trends. [link]
- Commits: Provides insights into commit patterns and file contributions. [link]
Pull Requests Section
The Pull Requests section offers a comprehensive view of your team’s pull request activity and efficiency:1. Pull Request Volume and Size
Value: Understand the overall workload and complexity of your team’s pull requests.
How to use:
- Monitor the total number of merged pull requests to gauge overall productivity.
- Analyze the trend in pull request size over time to identify potential complexity issues or improvements in code organization.
2. Pull Request Efficiency
Value: Assess the speed and efficiency of your team’s pull request process.
How to use:
- Track the average cycle time to identify bottlenecks in the review process.
- Monitor the number of file changes per pull request to balance between meaningful updates and manageable reviews.
- Look for correlations between PR size, file changes, and cycle time to optimize your development process.
3. Code Change Impact
Value: Visualize the net impact of code changes in production.
How to use:
- Assess the overall trend of code additions vs. deletions.
- Identify weeks with significant code churn and correlate with major feature releases or refactoring efforts.
Commits Section
The Commits section provides insights into the nature and distribution of code contributions:1. Commit Type Analysis
Value: Understand the balance between feature development and bug fixing efforts.
How to use:
- Monitor the ratio of feature commits to bug fix commits to assess development focus.
- Use this information to adjust resource allocation between new feature development and maintenance work.
2. Commit Trends
Value: Visualize commit patterns over time to identify productivity trends.
How to use:
- Analyze weekly commit patterns to understand your team’s development rhythm.
- Identify any seasonal trends or impacts from project phases on commit frequency.
3. File Contribution Analysis
Value: Identify the most frequently updated files and potential areas of technical debt.
How to use:
- Focus code review efforts on frequently changed files.
- Identify files with high bug fix contributions as candidates for refactoring or increased testing.
- Use this information to guide documentation efforts and knowledge sharing within the team.
How to Apply Filters
- Locate the “Select date range” dropdown at the top of both Pull Requests and Commits sections.
- Choose your desired time frame for analysis.
- The dashboard will automatically update to reflect your selection, allowing for focused analysis over specific periods.
