Git Tips

Stop piling up old branches. Learn the git bam (http://chrshnt.com/git-bam) command.

Git has many useful hooks (http://chrshnt.com/git-hook) and those hooks belong to you.

Tired of that boring, plain git log? Make it --pretty! See my gitconfig (https://git.io/v20Oi) for an example.

Having a tough time remembering the name of that emoji? Check out the mojibar (https://github.com/muan/mojibar).

Some of these you may not know about.

It does! You just have to tell to.

Working with documentation or a co-worker that loves to adjust whitespace across the entire project every time they open a PR? You're welcome.

Sometimes the diff isn't enough and you actually want to play with the code in a pull request. Here's how.

How to close issues like a professional when you open a pull request.

AKA: Make it look like you're working when you're not actually working.

How to break up all those changes into smaller commits for the poor soul that has to review your pull request.

Git doesn't want you to create an empty commit, but you can do it anyway.

Git knows where you've been and makes it easy to go there again.

I love GitHub, you love GitHub, but there are some hypothetical situations where it may not be available.

Ah, Saturday morning and I'm bored. What can I work on?

If you're already writing good commit messages, you already have a good pull request.

You don't need to send all notifications to the same email address.

Oops! Thank goodness git has undo.

Type too fast? Forget to add a file? Fix it later.

Make that thing you do all the time a git command.

Mark them as read - you don't actually have to read them :)

It you get a lot of email, this is for you.

Full speed ahead!

What is this all about?