Hello, class. I'm Mr. @Quinnypig, and I'll be your substitute teacher. Today we're going to learn about git.

The four interfaces of developer experience: APIs, CLIs, GUIs, and docs. Treat each as a product, so that those products can treat developers as customers 🤍

Really digging this slide-deck from @acemarke :

"git-vanquish-branch vanquishes various non-allotted upstream branches below various shown histories, and after a git-hammer-base (diffed by git-satisfy-tip and git-compile-change) fast-imports a history, uncleanly cloned indices are prevented for the user, and tips that were..."

If you haven't seen the git man page generator, check it out. I could sit here refreshing this page all day. https://t.co/n8FvfUQ16a #git

Add a new remote repo with: 'git remote add remote name' $ git remote add repo-for-reference git@github.com:someone/some-project.git Remotes aren't limited to "origin" and "upstream". Anyone out there have interesting use-cases?

also, who knew there were alternatives for how merge conflicts are presented? git config --global merge.conflictstyle=diff3

one gem from inside is this git alias: git config --global alias.please 'push --force-with-lease'

This article is worth a read: https://t.co/4L0bbEhd7r

I started writing a little toy script to mess with git commit hashes. Check it out:

Pretty sure @michaelgmcd introduced me to this. Thanks Mike!

I use `git commit --amend --no-edit` so often that I have it aliased as `git cane`. Super handy.

"Always be committing". Once committed, it's near impossible to lose your code. I'll often `git commit --amend --no-edit` to keep adding to a "draft" commit until its ready to push. Even though it overwrites the commit, you can always go back with `git reflog`.

pro-tip: version control a `.gitconfig` file and symlink it into your home directory. Here's mine!

$ git status On site twitter Your feed is up to date with 'origin/@git_log_oneline'.