What is Git? Your Magic Project Time Machine!

The afternoon sun slanted through the skylight of Gitty the Cat’s cozy attic studio, painting golden stripes across her cluttered workbench. Scattered everywhere were half-finished drawings, crumpled storybook pages, and stacks of colorful LEGO bricks, and right in the middle of it all sat Gitty, her fluffy orange tail twitching with frustration as she stared at her latest masterpiece: a rainbow castle with fluffy cloud turrets and a sparkly candy-striped drawbridge. She’d spent three whole weekends working on it for the school art show, and it was *almost* perfect—until her paw slipped on her cup of orange juice, and a big, sticky splatter landed right across the pink castle walls.

“NOOO!” Gitty yowled, her ears flattening against her head. She’d tried dabbing at it with a napkin, but the orange stain had already seeped into the paper, turning her perfect pink walls into a messy orange mess. She was this close to crying, until she remembered the coolest thing her grandpa had ever taught her: her very own time machine, called Git.

Grandpa had explained it like this, while they were building a LEGO spaceship last month: “Git is like a magic camera that takes a picture of your work every time you finish a little step. You can save as many pictures as you want, and if you ever mess up, you can hop right back to the picture you took before the mess happened. No redoing all your hard work required!”

Gitty’s eyes lit up. She tapped the little paw-shaped keyboard in front of her, and her special Git time machine (which looked a lot like a regular laptop, but had sparkly star stickers all over it, and a tiny plush mouse shaped like a fish) whirred to life. A list of “pictures” (Grandpa called them *snapshots*, but Gitty liked “time photos” better) popped up on the screen, each with a little date stamp and a note Gitty had written when she saved it:

• 🖼️ Time Photo 1: Rainbow Castle rough sketch (May 20, 10am) – just wobbly castle outlines, no color, note says “tried to draw the towers too pointy, will fix later”
• 🖼️ Time Photo 2: Rainbow Castle colored (May 21, 2pm) – pink walls, blue roof, no details yet, note says “finally got the pink right! Love this shade”
• 🖼️ Time Photo 3: Rainbow Castle finished (May 22, 4pm) – *this was the one with the orange juice splatter*, note says “added cloud turrets and candy drawbridge, done! …wait why is there orange on the wall?”

Gitty grinned and tapped “Go back to Time Photo 2”. The screen flashed for a second, and suddenly her file was back to the perfectly colored castle, no orange stain in sight. She immediately saved a new time photo, called “Rainbow Castle v4 – no juice edition!”, and moved the file to the far corner of her desk, right next to her stack of art supplies so no one would accidentally spill anything on it ever again. A week later, the art show judges gave her first place, and Gitty knew it was all thanks to her magic Git time machine.

<concept>版本控制 (Version Control)</concept> What Gitty just used is called *version control*, which is just a fancy grown-up term for “keeping track of every version of your work as you change it”. Think of it like this: when you write a story, you probably keep all your old drafts, right? The one with the messy first draft, the one where you fixed the spelling mistakes, the one where you added the cool dragon character – you keep all of them because you never know when you might want to go back to an old idea. Git does exactly that, but for *any* kind of project: drawings, stories, LEGO building plans, science experiment notes, even your Minecraft world saves! It automatically saves every little change you make, so you never have to worry about losing your work, even if you accidentally delete something, spill juice on it, or decide you hate the new dragon character you added and want to go back to the old version.

The best part? Git doesn’t just save the whole file every time, either. If you only change one small thing – like the color of the castle walls, or the name of your story’s main character – Git only saves that tiny change, not the whole entire file. That’s like if you wrote a 10-page story, and only fixed one spelling mistake on page 3: you don’t have to rewrite the whole 10 pages, you just make a tiny note that says “fixed ‘dragon’ to ‘drgon’ on page 3, oops”. Git does the same thing, which makes it super fast and saves a lot of space on your computer.

<example>Example 1: Saving your drawing versions</example> Let’s go back to Gitty’s rainbow castle to see how this works in real life, no computers required! Imagine you’re drawing a picture of your pet hamster, Sir Fluffington the Brave, for your classroom pet wall: 1. First, you draw a wobbly outline of Sir Fluffington, with a too-big head and too-short legs. You label this “Version 1: Rough Draft” and put it in your “Sir Fluffington Art Folder”. 2. Next, you color in his fur, his little pink nose, and his favorite sunflower snack. You label this “Version 2: Colored” and add it to the folder. 3. Then you add his tiny superhero cape, because he’s a brave hamster after all. You label this “Version 3: Super Hamster Edition” and add it to the folder. 4. Oh no! Your little brother runs past the table and knocks over your glue stick, which oozes all over Version 3, covering his cape in glue. If you didn’t save the old versions, you’d have to draw the whole hamster over again from scratch, which would take forever. But because you saved every version in your folder, you can just grab Version 2, add a new cape (this time keeping it away from the edge of the table!), and save it as Version 4. No redoing all that coloring work required!

That’s exactly what Git does, just automatically. Every time you finish a small step of your project, you tell Git “save a snapshot of what I have right now”, and it tucks that snapshot away in a special folder for your project, with a note about what you changed. If you ever mess up, you just pick the snapshot from before the mess, and you’re good to go.

<sidebar> 💡 Git小贴士 (Digital Edition Sidebar) Did you know Git is used by more than just artists and writers? Game developers use it to save every version of their Minecraft mods, so if a new update breaks their mod, they can go back to the old working version. Scientists use it to save their experiment notes, so if one test fails, they can go back to the notes from the successful test to see what they did differently. Even movie studios use version control to keep track of all the edits to their animated films! If you make *anything* that you might want to change later, Git can help you keep it safe. 👉 [Watch Gitty demonstrate time travel with her drawings (video)](/media/gitty-drawing-demo) </sidebar>

<example>Example 2: Collaborative class storybook</example> Now let’s see how Git helps when you’re working on a project with friends, which is one of its superpowers. Last month, Gitty’s class decided to write a group story called *The Great Third Grade Cheese Heist*, where each student writes one chapter about the class hamster, Sir Fluffington, going on an adventure to find the missing treasure chest of cheese in the school cafeteria.

There are 20 students in the class, so if they didn’t use Git, it would be a total mess: someone might accidentally delete another person’s chapter, two people might try to write the same scene at the same time, and if someone made a mistake (like writing that Sir Fluffington can fly, when the class agreed he can only jump 2 inches high), they’d have to go through every single chapter to fix it.

But with Git, every student gets their own little “workspace” to write their chapter, without touching anyone else’s work. Let’s look at what happened: 1. First, the teacher, Ms. Patel, creates the main project folder for the story, and writes the first page explaining who Sir Fluffington is. She saves a snapshot of this first page, called “v1: Story setup”. 2. Next, Leo writes Chapter 1, whe