How to Make Actually Good Commits in Git

Are your git commits plauged by vague commit messages? "Fixed some bugs"? "Added some things"? And inside, are your commits just a mishmash of random work? In this video, I'll teach you how to make good git commits that will make things clear for you and your team. No more endlessly searching through your git log looking for that one change somewhere in there...

0:00 Intro
0:36 How *not* to commit
3:27 Breaking down your git commits
6:03 Writing a good commit message
7:47 Conclusion

[bettercalldelta]

I feel violated receiving this in my recommended after pushing a commit titled "bruh"

[e.dani.f]

Thank you for this video! I’m a newbie and I spent way too much time trying to figure out how to write multiple lines in the terminal (-m more than once never occurred to me).

[utilyre]

I personally would rather to extend the commit message by not adding the quotation mark at the end. So when i press enter it adds a newline instead of running the command

[aditeya]

A better way to write git commit messages is using the conventional commits format. Tools like git-cz or rcz (rust based tool that i use) can be used to generate the message quickly. Though crafting a good commit is still based on your judgement.

[phatboislym]

great video, didn't know you could use the -m flag multiple times like that
curious about your prompt, what setup is that? I like the counters on the git tracks