How to commit better with Git

Commits are the visible blocks of work of a programmer’s craft. Yet it seems that so little effort goes toward crafting a good git commit. In this video, I will talk about why I think it is important to care more about the commits that we push into the world.

In this tutorial, I will talk about how you can write better commit messages and what the git best practices are, and how they relate to the GitHub commit message conventions. We will dissect the anatomy of a good commit message and look into how you can use interactive rebase to reformat and combine the commits you want to push to your git repository after the fact.

Questions of the day
■ Do you have rules for your commit messages?
■ What’s the most important point for you when it comes to commits?

Interactive Rebasing:

Sources:

---

This video contains advertising content.

---

Attribution:

#git #softwaredeveloper

[ev.c]

Once I got rejected on a job interview because my commit pattern and messages were bad. LOL

A lesson lived is a lesson learned.

[jewpcabra]

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!

[stefandillenburg]

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

[gentoomaniac]

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

[saadmansakib]

*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!

[DevOpsDirective]

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

[PhilipNorton]

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.

[AjaySingh-xdnz]

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.

[ghaithjr.]

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 !

[message]

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

[rebecaaras]

Great video, useful and straight foward. Thanks!

[filipecrosk]

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 :)

[kedotdev]

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

[hglbrg]

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

[NothingButBen]

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

[KieCodes]

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?

[shanashinigami]

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

[nils]

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!

[dragoncode]

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

[mikewise]

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:)