feature: gathering metrics about commit messages #103
Merged
Conversation
This file contains 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
…l statistics for all messages in particular repo added. Also prepared README for backend development
7 tasks
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: gathering metrics about commit messages and preparing overall statistics for all messages in particular repo added. Also prepared README for backend development.
Now before closing repo as analysed besides analysing all files in repository we also are gathering metrics about each commit message, we are calculating basic features like message length, words amount, gunning fog index and type of commit (FEATURE, FIX, MERGE PR, CONFIG CHANGE, UNCLASSIFIED). Then for entire repository we are calculating statistics abut commit messages from which the most important is ratio of meaningful messages (classified as feature, fix, merge or conf change) to non-meaningful ones (unclassified). For now classification is based on keywords present in a message but it can be easily replaced at any time because we are storing in DB all information that is needed to recalculate all metrics if needed.
Panels in Graphana were also updated: