Skip to content
This repository was archived by the owner on Jan 19, 2021. It is now read-only.
This repository was archived by the owner on Jan 19, 2021. It is now read-only.

Gather pull request analytics #47

@aexvir

Description

@aexvir

As this was one of the main motivations for this project, we definitely need to focus on this :D

The metrics we'll be gathering initially will be

  • Time the merge request has been on review (1)
  • Pull request author
  • Pull request reviewers / approvers
  • Merge request intention (2)
  • Merge request areas (3)
  • Amount of LoC changes (added and removed)
  • Amount of comments
  • Amount of commits
  1. The review time might be tricky to calculate, so we'll need to make some assumptions. I'm proposing the following:

GitHub: The review time will be calculated since the first reviewer has been added until the last reviewer has agreed or the PR has been merged. Draft MRs will be considered unreviewed even if there is a reviewer set (by some automation for example).

GitLab: The review time will be calculated since the first approver has been added until the MR is approved. WIP MRs will also be considered unreviewed even if there is a reviewer set.

  1. The intention will be determined by checking the conventional commits commit types. We'll use some heuristics to determine it. I'm proposing the following:
Type Commits
Maintenance build | ci | chore | style | test
Bug fix fix + ((maintenance) | docs)
Feature feat + ((maintenance) | docs)
Improvement? refactor | perf + (maintenance)
Documentation docs
  1. Gathered from conventional commits, that's it, no fancy stuff

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions