We care about a clean and understandable history of changes as it makes our life easier. I’d like to share our best-practices with advanced git techniques, as well as explain the reasons we think it’s worth the extra effort to maintain it. What does a good commit look like? How to create a helpful commit message? For whom am I even writing the message? I’ll explain our workflow, amending commits, squashing, interactive rebasing, and creating aliases for frequently used commands and share real-world examples of how it helped us in the long run. You should be already familiar with the basics of git (commit, pull, push, merge) if you want to get the most from the talk.