Github on t0ul

Introducing Git and GitHub the Safe Way

Sun, 18 Oct 2026 00:00:00 +0000

Most git tutorials teach you to type the commands. This one teaches you the commands and the four habits that the commands alone do not give you. It is for people who have just started to code, or who have been coding for years and still feel that git is a thing that happens to them.

The four promises

By the end of nine short chapters you will be able to keep these, on your own projects and on anyone else’s:

Git and GitHub the Safe Way, Ch. 1: Snapshots, Not Sync

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

People get into trouble with git because they think it is something it is not. Three wrong pictures account for most of the pain, and it is worth naming them before learning a single command.

Three things git is not

It is not a sync folder. Dropbox and iCloud copy whatever is in a folder, continuously, whether you meant it or not. git copies nothing until you ask, and it copies exactly what you asked for. That is the whole point: a secret that is in your folder is not in git until you put it there, and a change you did not mean to make is not in the history until you commit it. Everything in chapters 3 and 4 depends on that gap.

Git and GitHub the Safe Way, Ch. 2: Setup That Lasts

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Twenty minutes, once per machine. Everything here is written to a file in your home folder called .gitconfig, and at the end of the chapter you will read that file and understand every line. Nothing in it is hard; most people simply never do it, and then spend years typing a password for every push and wondering why their commits show up under the wrong name.

Git and GitHub the Safe Way, Ch. 3: The Daily Loop

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Chapter 1 said safety is mostly looking before each step. This chapter is the loop those looks live in. If you know add and commit already, the new parts are staging part of a file, writing a message that will still mean something next year, and the one habit that stops most secrets at the door.

Git and GitHub the Safe Way, Ch. 4: Secrets Never Go In

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Promise one. A committed secret is the most expensive mistake in this book, because it is the only one git cannot undo: a key that was public for four minutes may already be in someone’s scraper, in a fork, in a CI log. So the work happens before the commit, in layers, and the last layer is knowing what to do when all the others failed.

Git and GitHub the Safe Way, Ch. 5: Branches and Pull Requests

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Until now every commit went straight onto main. That is fine alone, on a project nobody depends on. The moment a second person, or a deployed copy, or a future you depends on main being right, changes need somewhere to live while they are half done and somewhere to be read before they count. That is a branch, and a pull request is the reading.

Git and GitHub the Safe Way, Ch. 6: Protecting main

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Chapter 5 described a way of working: branch, pull request, review, merge. This chapter makes GitHub insist on it. Promise three, nothing changes on main by surprise, is a setting, not a resolution, and it takes ten minutes.

Git and GitHub the Safe Way, Ch. 7: Reading a Pull Request Like a Security Person

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Chapter 6 made a review mandatory. A review is only worth what the reviewer actually reads, and most pull requests are approved after a scroll. This chapter is how a security-minded person reads one, which turns out to be the same way a careful engineer reads one, with the order of attention changed.

Git and GitHub the Safe Way, Ch. 8: When It Goes Wrong

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Promise two was that no work is ever lost. This chapter is how git keeps it. There is an undo for every stage a change can be in, and the trick is matching the rung to the mistake. Climb no higher than you need: each rung up rewrites a little more, and the top rungs rewrite history that other people may already have.

Git and GitHub the Safe Way, Ch. 9: GitHub Hygiene

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Promise four: nobody acts as you. Everything in the previous chapters assumed that a push from your account was you. This chapter is the settings that make that true, and the few repository switches that let GitHub watch your back. Most of it is done once; the last section is a yearly habit. Button names follow GitHub’s documentation on the day of writing, linked in each section.

Git and GitHub the Safe Way: The One-Page Cheat Sheet

Sun, 18 Oct 2026 00:00:00 +0000

Part of Git and GitHub the Safe Way, a short book on git, GitHub, and the habits that keep a repository from hurting you.

Setup, once per machine (chapter 2)

Do	Command or place
name and email	`git config --global user.name "Ada Gopher"`, `git config --global user.email "ada@example.com"`
start on main	`git config --global init.defaultBranch main`
an editor you can exit	`git config --global core.editor "code --wait"`
make a key	`ssh-keygen -t ed25519 -C "ada@example.com"`
give GitHub the public key	Settings, SSH and GPG keys, New SSH key (once as authentication, once as signing)
test it	`ssh -T git@github.com`
sign every commit	`git config --global gpg.format ssh`, `git config --global user.signingkey ~/.ssh/id_ed25519.pub`, `git config --global commit.gpgsign true`
ignore OS and editor junk everywhere	`git config --global core.excludesFile ~/.gitignore_global`

The loop (chapter 3)

Do	Command
what changed	`git status --short`, `git diff`
stage part of a file	`git add -p file`
what the next commit will contain	`git diff --staged`
commit	`git commit -m "Do one thing"` (add `-m "why"` for a body)
history	`git log --oneline`, `git log -1 --stat`, `git log --oneline --graph --all`
per-project ignores	`.gitignore`, written before the first `git add .`

Secrets (chapter 4)

Example keys from a provider’s documentation are deliberately ignored by scanners; test with a randomly generated string.