You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the enhancement
Another interesting metric would be the number of git commits done on a file. Files which get touched a lot (hotspots) can indicate complicated / high maintenance code. On the contrary, files which only got touched once or twice and are reasonable complex could indicate a lack of auditing or refinement.
I have thought about this, and I think it best served by another tool, which may include scc as a library or some such. Ripsrc did this to an extent https://github.com/pinpt/ripsrc
I don't know if I am willing to implement this myself, although its something I think I might need in the future with some ideas I have so you never know.
Describe the enhancement
Another interesting metric would be the number of git commits done on a file. Files which get touched a lot (hotspots) can indicate complicated / high maintenance code. On the contrary, files which only got touched once or twice and are reasonable complex could indicate a lack of auditing or refinement.
Cf. https://www.infoq.com/presentations/code-bugs-legacy-pitfalls/
Example
Thanks for considering.
Cheers!
/Doomguy
The text was updated successfully, but these errors were encountered: