How to commit better with Git 

Once I got rejected on a job interview because my commit pattern and messages were bad. LOL A lesson lived is a lesson learned.

I seriously need to share this with all my coworkers... I'm the only person who uses git rebasing, squashing etc - this is such important info! Great way of describing, I hope more people follow this!

Interactive rebasing - made my day. Thanks for introducing this feature, didn't know about it in the first place. Keep going!

Good video! One of the most important things for me is a ticket number at the start of the commit message. This points the commit back to even more context than the commit message contains. What has been done should be in the commit, why it was done should really be in the ticket.

*To the community* I landed a software engineering job this month and studied about "conventional commits". My commits started to have more meaning and context as a result I got praised by my seniors. If you're wondering how to write good commits which adds value to them, please look at "Conventional Commits". *To Kie* Thank you so much for this video, learned a lot of new stuffs. Subscribed!

you successfully nailed to share with us the feeling you had when you experienced a bad commit history and how annoying it was haha , great video !

This video is a great resource!

This is a great, compressed talk on the most important things.

I want to send this to my BOSS!

Great video, useful and straight foward. Thanks!

The world is so small. From your accent, I knew you're german. But then I opened your website and saw that you're also like me from Hamburg 😅 Very good video. I'd love to work with folks who could appreciate a good commit like that! Subbed!

Subscribed -- for being your second video, this is awesome! Quality content, solid script, good edit... Keep it up!

Preach imperative mood. I don't care what YOU did in your work day, I want to know what the commit will do if I apply it. Also imagine trying to find where the fuck a bug started when all commits look like "fix some stuff" "change things" "add new feature"... yeah

Well done Kie. I gave a quick presentation another day inside my company about it. Good commit messages matter, a lot! haha thanks for sharing it :)

Very nicely explained. Precise and organized content, like a good commit message ;) You explained it under 12 mins what many tutorials don't do in hrs! Thanks.

Hey everyone! It's Monday again. Time for a new video. This time I want to talk about Git Hygiene and how to use Git better! Let me know: Do you have rules for your Git usage?

this is so on point and helps a lot thank you for sharing and the effort 👏👍

Awesome video!

Great video. Great production quality. I'd love to see more content from you.

Very nicely explained stuff. Now I totally understand when to commit and how to commit. Thank you

Great video. I learned so much thing in this video. Thanks a lot.

Excelent, thanks a lot.

Such a helpful video! And entertaining too. Thanks ♥️

Very nice video! I'm shocked you have under 100 subscribers!

The most important part is to understand that if you use git squash or rebase incorrect then you'll be in much deeper troubles than if you use shitty message.

Amazing! Thanks a lot ❤

Nice one. Learned something. Maybe two videos one explaining the branch and merge strategies and one explaining the rules for a commit message would have been better didacticly though... although I suspect the 10 minute rule played a role. Been using git for years myself, but not correctly:)

Do you have resources or are you able to explain more what you are talking about with private branches at 3:21? I'm not familiar with the workflow whereby your commits don't show up elsewhere

Great video, I'm going to share it with my partners

All good info for a good commit message to be sure, but one pattern in industry to consider is that when merging a pull request to master, it is often common to use a merge strategy of squash and rebase, which means all of your checkpoint commits will get squashed down automatically by GitHub or whatever else you are using, and you'll have the option to modify the commit message from within the browser environment as you perform the merge. This makes doing an interactive rebase to clean up your commits unnecessary, and means that most of the time, you won't have to worry about writing good commit messages for anyone except yourself.

Rule 8: Add relevant ticket numbers or links to references at the bottom of the commit message.

Some don't agree, but I always recommend 'git pull - - rebase' instead of 'git pull'. Combined with squash it make a good history.

5:57 but doing that, one can only make file-based commits. Cannot split different changes in the same file into separate commits, right?

A couple of my rules: 1. Don't use the words "and" or "as well" etc. in your message. That means your commit isn't atomic. E.g.: "a new constant has been added as well". 2. Don't paraphrase your code. You kinda say that by saying "explain what and why, but now how". And yet you add "a new constant IMPLEMENTATION_DETAIL with value 9000 has been added". Don't do that. Explain why you are doing that. 3. One trick that I use for my commit subjects is to try to take it up one level of abstraction. That helps to explain why and not how. 4. To make sure that others will understand my commit, I ask myself this question: "how could someone misunderstand what I wrote?", instead of patting myself in the back saying "that's a beautiful commit". 5. Don't squash. Just do not squash. I prefer having to deal with a small change titled "WIP toilet break" than this same change squashed into a huge commit, may it have an amazing description. 6. I don't recommend doing your method 3, because I know that in practice people won't do that. They'll be lazy and just make one giant commit. The only practical way I know of is to do your good commits as you go. If you don't, you won't do it later. Having to git add little bits of paragraphs, or worse, pieces of lines, in different commits, really isn't fun. So make little WIP checkpoints commits if you want to (I sometimes do that, although rarely), but as soon as you have your atomic change, squash NOW with a good message and push. 7. Quote quoted text. That's both in code and in commit messages. "new database field awesomeness": is that the actual name of the field, or is that a joke of some sort? I literally don't know. If it's the name of something, the message should be "" new database field "awesomeness" "". I'd love to hear what you think about these.

Glad to see other people who take git commit message content seriously. I pretty much follow all of your rules, but one that I use is that if my summary has to include the connective "and" or "or" then it's doing too much and I need to break it up. One of my team-mates gave a presentation on our development approach that includes how we do things with git: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-qTVeWbg2tKk.html .. it aligns with much of the things in this video.

Man hört sofort raus, dass Du deutsch bist 😜 Aber super hilfreich

Amazing, Thanks a lot for the video