Module 6 · Publish to GitHub
Publish your project to GitHub
Stage 5. Your site is great — now we back it up to the cloud with GitHub, the free, safe home for your project. This also sets up the one-click publishing you’ll use in the next module.
Watch — hand-picked
The clearest walkthroughs of this step, from creators we rate. Each one’s credited — go give them a follow.
How To Use GitHub For Beginners
GitHub Basics Made Easy: A Fast Beginner's Tutorial!
A brief introduction to Git for beginners | GitHub
The big picture
GitHub keeps a backed-up copy of your project and a history of every version — if your laptop ever dies, your site is safe. The one real gotcha is connecting your computer to GitHub (authenticating), which trips up almost everyone who skips it. The prompt below has Claude do it properly with a simple browser sign-in.
First, create a free GitHub account
If you don’t have one, go to github.com and sign up (it’s free). Then come back.
Paste this into Claude Code
Back up to GitHub
Let's do Stage 5 — publish my project to GitHub. Please follow your deploy skill: 1. Connect this computer to my GitHub account properly. If the GitHub CLI (gh) isn't installed, install it, then run "gh auth login" and walk me through it step by step — I'll choose GitHub.com, HTTPS, and "log in with a web browser." Tell me exactly what to click. 2. Make sure there's a good .gitignore so we never upload anything private or junk. 3. Commit my work, create a new private GitHub repository, and push my project to it. 4. Give me the link to view my project on github.com. I'm not technical — do the technical parts for me and keep it simple.
What you’ll do
- Claude installs the GitHub CLI and starts the sign-in (approve when asked).
- A short code appears (like
AB12-CD34). Copy it; a browser opens; paste it and click Authorize. This is a once-ever step. - Claude creates your repository and uploads everything. Refresh github.com and your files are there.
You probably don’t have any of these yet — this is just good to know. Some files should never be uploaded: passwords, private keys, and the giant node_modules folder. Claude sets up a .gitignore that skips them automatically.
Your project lives safely on GitHub and your computer is connected for all future updates. One module to go: making it live on the internet.
See an error like Support for password authentication was removed or a rejected push? The sign-in didn’t finish. Tell Claude: “GitHub won’t let me push — please run gh auth login again and walk me through it.” Re-doing the browser sign-in fixes it almost every time.