📚 Topic Summary
Version control is like a super-powered 'save game' feature for projects. Imagine you're building with LEGOs. You make a cool tower, but then try to add a spaceship and it all collapses. Version control lets you go back to your saved tower before the spaceship disaster! It tracks every change you make, who made it, and when. This is super helpful when many people are working on the same project, or when you want to experiment without breaking everything.
Unplugged version control means learning these concepts with simple, hands-on activities – no computer needed! We'll use paper, pens, and maybe some LEGOs to understand how it works. Let's get started!
🧠 Part A: Vocabulary
Match the term with its definition:
| Term |
Definition |
| 1. Repository |
A. A set of changes made to a file or files. |
| 2. Commit |
B. A copy of the project at a specific point in time. |
| 3. Version |
C. A place where your project and all its history are stored. |
| 4. Merge |
D. Combining changes from different versions. |
| 5. Branch |
E. An independent line of development. |
✏️ Part B: Fill in the Blanks
Fill in the blanks with the correct words from the word bank: version, repository, commit, merge, branch.
A _________ is like creating a new timeline in your project. When you make a _________, you're saving a snapshot of your work. All the files for your project are stored in a _________. To combine work from different lines of development, you _________ them. Each save is called a _________.
🤔 Part C: Critical Thinking
Imagine you're working on a group project to write a story. How could you use version control principles (even without a computer) to make sure everyone's contributions are organized and no one loses their work?