Code analytics
Include more reports in EE that are related to groups, projects and files within projects, pick from:
- https://gitlab.com/gitlab-org/gitlab-ee/issues/413 Code coverage over time
- Developer churn (how many developers worked on the same piece of code, useful when managing contractors)
- Code hotspots (code that sees a lot of churn)
- https://gitlab.com/gitlab-org/gitlab-ee/issues/91 Burndown charts (based on issue weight)
- Bus factor (active pieces of code/projects with few developers contributing)
- Test coverage for pieces of code
- Issues (bugs) opened for pieces of code
- Complexity of pieces of code
- Code added just before release (is the release stable or not)
- How many people worked on a piece of code
- When where pieces of code modified (when did development start and end)
Also include a suggestion to make a request to us if they need more.
https://gitprime.com/ is a good example of measuring productivity and code hotspots
Also see Delivery analytics gitlab-org/gitlab-ee#110 and Contribution analytics gitlab-org/gitlab-ee#109
We should consider providing insight on the branch level, see https://news.ycombinator.com/item?id=10934970
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.