Rénald Casagraude kipit

I've spent the day trying to get this setup working with GitHub and given the number of gotcha's I encountered, it seemed like a good idea to document how I finally got this working with as few hacks as possible. There's a lot of documentation out there (some of it old and misleading) and committing here for posterity will help me remember this when I inevitably need to do this again.

Rationale

Passwords are simply not enough these days. Regardless of the company, breaches (and the associated Personally Identifiable Information harvested) are a matter of not if, but when. There are a number of things you can do to protect yourself, but being on the tin-foil-hat side of paranoia, means there are a few Commandents that I adhere to (and recommend for other folks)[Insert link to Fight Club Rules for the Secure Internet].

That being said, if you use 2-factor authentication and have committed to using a hardware token such as the Yubikey, then you're already ahead of the curve. The problem is that wh

	I once read an https://bit-booster.com/doing-git-wrong/2017/01/02/git-init-empty/ , about why
	you should start with an empty commit for a new repo. The page has since then dissapperard but I got
	some of it out of the wayback machine and archive it here:

	Always Start With An Empty Commit
	Whenever you start a new git repo, pop an empty commit onto it before you do anything else!

	git init new-repo
	cd new-repo
	git commit -m 'initial empty commit' --allow-empty