Git Etiquette: Make your coworkers happy, be ready for CD and grow as a developer!

Let me show you on a real-life example why the way you use git makes a difference. This is not your standard git tutorial video. In fact I won't be using the git command line tool once. Instead this is about the mindset behind using git. How should you structure your commits? What makes a good commit? What is a good commit message? And most importantly: Why should I care? I'll try to explain to you why I believe for someone to be considered a senior developer they must be able to make great commits!

[NavyaTeja]

Yes, of course I would like to see some react videos....may be like....one on redux, one on duck pattern something like this.

[norm]

Do you have a script to reproduce your lovely Shell Look & Feel?

Thanks for the great videos.

[ianpan]

Nice Video! May I know what **Window Manager** you are using on macOS?

[FalconFetus]

So you want me to make small, frequent commits, AND write a long motivation for each one? Sorry, but if I did that I'd be spending more time writing commit messages than changing code.