A list of cool features of Git and GitHub
github.com
github.com
Don't do this. The default (since 1.8.4) is auto, which adds colors if the output goes to a terminal, but doesn't if the output goes somewhere else (e.g., a pipe). That is probably what you want (and already have).
I fell for this myself at some point. Somehow expecting there to be more colors, or full color support, or something like that — Nope.
> The default setting is auto, which colors output when it’s going straight to a terminal, but omits the color-control codes when the output is redirected to a pipe or a file.
> You can also set it to always to ignore the difference between terminals and pipes. You’ll rarely want this; in most scenarios, if you want color codes in your redirected output, you can instead pass a --color flag to the Git command to force it to use color codes. The default setting is almost always what you’ll want.
git config --global --unset color.uiTo install on Mac just run:
git clone https://github.com/mathiasbynens/dotfiles.git && cd dotfiles && source bootstrap.shIt links to a GitHub repo [1] I made a while ago with every type of emoji as a separate file and commit as a fun and somewhat pointless demo.
However, for whatever reason the emojis on the repo stopped working (after a GitHub update?). Each emoji, regardless of commit message, is defaulting to the last one that was created (:zzz:). I reached out to GitHub a few times about it, but I never got a response. It's probably super low priority for them, but I thought I would share since, although minor, I technically broke GitHub.
Emojis make everything a little bit fun.
$ git instaweb
Wow! Git never ceases to amaze! http://git-scm.com/docs/git-instawebHey, can't I git rebase --root?
More like a shouldn't (or really shouldn't if you will) than cannot.
tldr; you have to set the hook yourself
Annoyingly, this doesn't work for pull requests.