Tell a story with your (git) repository
Ever found yourself searching for *that commit* that broke everything? Trying to analyse project history and learn why something was done that way? Maybe all you see is a list of "fixed this" and "fixed that" messages that makes you want to start over? Want to know how can you do it better?
Repository history is often overlooked as a tool to keep information about project development process. I'd like to share my experience in keeping and encouraging discipline among engineers to not only keep the code clean, but also care about what goes into VCS.
Delivered in English
Check out the rest of talks of SymfonyLive London 2016 conference.