Open ChristopherBanas opened 2 years ago
https://github.com/garybernhardt/dotfiles/blob/main/bin/git-churn. good article explaining it here https://textexpander.com/blog/what-is-code-churn-and-how-to-reduce-it
git log --numstat
shows number of added and deleted lines in decimal notation and pathname without abbreviation, to make it more machine friendly https://git-scm.com/docs/git-log#Documentation/git-log.txt---numstat
I did not find much info on git churn
it seemed to be a very specific add on command that wasn't discussed much. I did learn what code churn was though haha.
Git log seems to be the most popular form of seeing how and what is being changed in each file within each commit
https://github.com/andymeneely/git-churn the one we want
Ticket is a WIP
Motivation Git-churn is the tool that can generate the json needed. But it does not know anything about vulnerabilities, just does overwrite analysis. In order to automate it, we have to check "do I have the overwrite analysis" in the vulnerability repo, if we do then skip. If not then look at fix commit, vcc commit..., others?
Screenshots
Additional context
Check the following: