Download to read offline
Uploaded byRaimonds Simanovskis
Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015
This document discusses analyzing and visualizing git commit logs to gain insights. It provides examples of visualizing commit data by time, authors, files changed, and other dimensions. Examples shown include contributions over time to Rails and Node.js, top contributors, and analyzing patterns in commit times. The document advocates using git logs for code metrics and "Mining" them to learn from a codebase's history.
Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015
- 1. Analyze and Visualize GitLog For Fun and Profit Raimonds Simanovskis @rsim
- 2.
- 3.
- 4.
- 5. Mining Rails — Learningfrom your App’s Lifeline Michael Feathers, Corey Haines RailsConf 2011
- 6.
- 7. Ruby on RailsGit Log
- 8. Changes in Rubyfiles Birth of Rails Great Rails 3 refactoring RailsConf is coming
- 9. DHH contribution Rails ismine Let others contribute too Car racing takes all my time… OMG! I should give a technical talk at RailsConf! Don’t make this mistake anymore
- 10. Top contributors in2015 by number of commits
- 11.
- 12. 9-to-5 disciplined developer Hours ofday warms up with small commits eats lunch at 12pm finishes work and socializes Aaron Patterson
- 13. Don’t judge someone bytheir appearance Hours of day @tenderlove
- 14. Don’t burn yourself! Hours ofday José Valim Why don’t you sleep? Ruby on Rails contribution in 2012 Working on Elixir? Get angry and start deleting code?
- 15. Finding the best workingpattern Hours of day Elixir contribution in 2015 José Valim
- 16. Contributions by time zonein 2015 US West coast Brasil Europe Japan India
- 17. Changes per dayof week in 2015
- 18. Changes per hour onFridays, in 2015 Beer time BDD
- 19. Linux > 0.5M commits >20M lines of code > 70M lines of changes > 14K contributors
- 20. Changes over time Jan1 1970 Apr 25 2037
- 21. Changes over time Jan1 1970 Apr 25 2037 Apr 16 2005 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
- 22.
- 23. What is thislarge C++, C, Assembler project?
- 24. Changes over time Really? >4M LOC?
- 25. Changes over time Really? >4M LOC? #### Dependencies Node.js has several bundled dependencies in the *deps/* and the *tools/* directories that are not part of the project proper. Any changes to files in those directories or its subdirectories should be sent to their respective projects. Do not send your patch to us, we cannot accept it.
- 26.
- 27.
- 28.
- 29. Ryan Dahl Creator ofNode.js
- 30.
- 31.
- 32. John Resig Creator ofjQuery
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39. There are only 2hard things in CS Naming things Cache invalidation Off by one errors Time zones Unicode special characters
- 40.