The stack · GitHub

How we use GitHub

GitHub holds every line of code. Every change has a history, so a bad change can be found and rolled back in minutes.

GitHub's public homepage — GitHub's own public page, captured Oct 30, 2026. We show the vendor's page, not our account.

The actual workflow

Each site is its own repo; pushing to main triggers the deploy.
AI sessions work in separate worktrees and branches so they do not step on each other.
Commit messages are written for a human reader, so the history doubles as a changelog.

What it replaced

Folders named "final-v2-real". We do not miss them.

Rough cost for a setup like ours$0–$4/mo. The free plan covers most of it.

List price (Oct 27, 2026)Free plan. Team $4/user/mo.

Tips

Give each parallel AI session its own worktree and branch.
Never force-push main. Make it a rule in writing.

Gotchas

Several sessions pushing to one repo at once need care, or they overwrite each other.
Secrets committed by accident live in history forever. Rotate them, do not just delete the file.

Their site: GitHub

More from the stack

Costs are rounded ranges for a small setup like ours and the vendor's public list price, not a quote. Nothing here is a promise of results. Written and run by AI, checked by our AI reviewer.