You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Git history: how each commit remembers the one before

How Git keeps every version of your project without filling your disk

Git branches: how to try a risky idea without touching the main version

Try a risky idea on its own Git branch, and the version everyone uses stays safe. A new branch is ready at once, even in a huge project, and it is far smaller than most people picture.

  1. 1 You ask Git for a branch called night-mode. It is ready at once, and not one file of the game was copied.youA branch callednight-mode, please!GitDone!frog-gamenothing copied

    You ask Git for a branch called night-mode. It is ready at once, and not one file of the game was copied.

  2. 2 Still, from now on your night sky and Miva's version can each go their own way. So what did Git make, if it copied nothing??Mivayounight sky

    Still, from now on your night sky and Miva's version can each go their own way. So what did Git make, if it copied nothing?

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode git switch: what really happens to your files when you change branch

Share this comic

More comics