Why Source Control?

Source control isn't just for software developers — it's for anyone who creates things that change over time and matter to the business.

The Problem We've All Had

Git solves this: One file, complete history. Every version is preserved with a clear message explaining what changed and why.

What is a Commit?

A snapshot of your work at a specific point in time

Each commit records:

• What changed (the diff)
• Who made the change (the author)
• When it happened (the timestamp)
• Why it was made (the commit message)

Think of it like a save point in a video game — you can always come back to it.

How Fabric + Git Works

• Commit — push changes from your workspace to Git
• Update — pull changes from Git into your workspace
• Fabric serializes each item as files/folders in the repo

Change Tracking in Fabric

When something changes, Fabric tells you:

These indicators appear in the workspace item list and the Source control panel.

Writing Good Commit Messages

Tips: Be specific, use present tense, keep the first line short (~50 chars)

Undoing Mistakes

Your safety net: Undo discards uncommitted changes and restores from Git

Scenario	Use Undo?
Uncommitted changes you don't want	Yes
Want to start fresh from last commit	Yes
Already committed the changes	No — use Pull Requests (Section 4)

What You'll Do in Section 1

Let's get started!