Conversation
afb4ef1 to
5a29a51
Compare
d39cd1d to
3e95955
Compare
3e95955 to
2976072
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Feature: Association rule metrics for Git History
Previously, only the commit count existed for files that co-changed (pairwise) together. Even if this is very intuitive it is biased towards files that change very often (README, pom.xml, ....). Now, a couple of other metrics like Confidence, Lift and Jaccard Similarity from the field of association rule learning are available and integrated in existing and newly added reports. Questions like "which files change together surprisingly often?" can now be answered with CSV reports and even visually in a treemap.
⚙️ Optimization