git-references

< Git References

CONFIG SETUP FOR A NEW INSTALLATION OF GIT

check current user information

git config --global user.name     
git config --global user.email

set current user information

git config --global user.name "Username"     
git config --global user.email "your.email@example.com"

for me:

git config --global user.name "crybx"     
git config --global user.email "crybx@users.noreply.github.com"

set user for single repo

from within the repo:

git config user.name "Username"
git config user.email "your.email@example.com"

default settings I like

git config --global pull.rebase true
git config --global fetch.prune true
git config --global diff.colorMoved zebra

These are:

• Pull with Rebase
• Prune on Fetch
• Differentiate Moved Lines - changed colors in diff for “moves”

check line endings setting

git config core.autocrlf

set line endings setting

git config core.autocrlf <true/false/input>

• false means don’t convert anything
• true converts LF to CRLF on checkout and all line ending to LF on commit, and is what people say Windows users should use
• input means pull line endings as they are in the repo but convert to LF on commit

Windows can handle CRLF (\r\n) or LF (\n), Mac and Linux use just LF.

I’ve read so much about git and line endings, and I don’t like any of the options. Why is there no convert to LF on checkout AND commit? That’s what I want. Just…use the one that works everywhere and don’t give me warnings about line conversions.

I use input though, even working on Windows. The editors I use let me set my line endings as LF or CRLF, so I set mine to LF. This way, I see no warnings about line endings and everything is consistent.

generate an SSH key for GitHub

On pc, per GitHub’s instructions (use the email you would use to log in to GitHub):

ssh-keygen -t ed25519 -C "your_email@example.com"

Note: If you are using a legacy system that doesn’t support the Ed25519 algorithm, use:

ssh-keygen -t rsa -b 4096 -C "your.email@example.com"

copy the contents of the id_ed25519.pub file to your clipboard (for pasting in to GitHub):

pbcopy < ~/.ssh/id_ed25519.pub

generate an SSH key

on pc:

ssh-keygen -t rsa -C "your.email@example.com"

add key to server (on a Linux box serving as a Git server):

cat ~/.ssh/id_rsa.pub | ssh user@hostname 'cat >> ~/.ssh/authorized_keys'

see all your config values and where they are set

git config --list --show-origin