In this short talk I outline why it is so important to keep track of the intent of your code changes if you want to be able to continue to change your project in Future. I then explain why your source control commit messages are such a good place to record this intent and highlight the practices that you can use to make your commit messages tell a valuable story about the changes you make.

Further reading

Reactions

Fantastic, succinct source control presentation from @joelchippindale #leaddev

@psyked

I really have taken @joelchippindale’s commit message recommendations—www.slideshare.net/joelchippindal…—to heart: github.com/altmetric/embi…

@mudge

@joelchippindale since your talk at @lrug I’ve been learning lots more Git. Proper commits, using rebase -i, squashing and more. Thank you!

@adrjohnston