Next Steps: Master Version Control

Once you've built your first app, Git becomes your safety net. Learn how version control lets you experiment freely without fear of breaking things.

Why Git Changes Everything

The Problem Without Version Control

You've built your to-do app. It works! Now you want to add a new feature, but you're worried:

  • "What if I break something and can't get back to the working version?"
  • "Should I save a copy called todo-app-backup-v2-final-FINAL.html?"
  • "How do I try different approaches without losing my progress?"

This fear holds you back from experimenting. Git solves this completely.

What Git Does

  • Snapshots - Save the exact state of your code at any moment
  • Time Travel - Go back to any previous version instantly
  • Branching - Try new ideas without affecting your working code
  • Collaboration - Work with others without conflicts

Why It Matters for Software 2.0

  • AI generates different solutions each time - save what works
  • Experiment with AI suggestions fearlessly
  • Keep working versions while testing improvements
  • Share your tools with others via GitHub

Git Basics: The Core Concepts

Think of Git Like a Video Game Save System

1. Commit = Save

Create a "save point" of your code at its current state. You can always come back to any commit.

2. Branch = Alternate Timeline

Create a parallel version to try new things. If it works, merge it back. If not, delete it.

3. Repository = Save File

The container holding all your commits and branches. Lives on your computer and (optionally) on GitHub.

Getting Started with GitHub Desktop

GitHub Desktop is the easiest way to use Git—no command line needed. It's free and works on Mac and Windows.

Step 1: Install GitHub Desktop

  1. Go to desktop.github.com
  2. Download and install for your operating system
  3. Sign in with a GitHub account (create one for free if needed)

Step 2: Create Your First Repository

  1. Open GitHub Desktop
  2. Click "Create a New Repository on your hard drive"
  3. Name it (e.g., "my-todo-app")
  4. Choose where to save it
  5. Click "Create Repository"

What just happened? You created a folder with Git tracking enabled. Any files you put here can now be version-controlled.

Step 3: Add Your To-Do App

  1. Copy your todo-app.html file into the repository folder
  2. GitHub Desktop will detect the new file
  3. In the bottom left, write a commit message (e.g., "Initial working to-do app")
  4. Click "Commit to main"

Congratulations! You just created your first commit—a snapshot you can always return to.

Step 4: Make Changes Safely

  1. Open todo-app.html in your editor
  2. Make some changes (try changing colors or adding a feature)
  3. Save the file
  4. Go back to GitHub Desktop—it shows you exactly what changed
  5. Write a commit message (e.g., "Changed color scheme to blue")
  6. Click "Commit to main"

Key insight: You now have TWO versions saved. If the new changes break something, you can always go back to the previous commit.

Step 5: Time Travel (Viewing History)

  1. In GitHub Desktop, click the "History" tab
  2. You'll see all your commits listed
  3. Click on any commit to see what changed
  4. To go back to a previous version, right-click and choose "Revert Changes in Commit"

This is powerful: You can never truly "break" your code. Every version is preserved.

Step 6 (Optional): Publish to GitHub

  1. Click "Publish repository" in GitHub Desktop
  2. Choose whether to make it public or private
  3. Click "Publish Repository"

Benefits: Your code is now backed up online, you can access it from anywhere, and you can share it with others.

Common Workflows for Software 2.0 Development

Workflow 1: Experimenting with AI Suggestions

  1. Make sure your current code is committed
  2. Ask Gemini for an improvement
  3. Replace your code with the new AI-generated code
  4. Test it
  5. If it works: Commit with a descriptive message
  6. If it doesn't: Right-click in GitHub Desktop → "Discard changes" → Your old version is back!

Workflow 2: Trying Major Changes

  1. Create a new branch (Branch → New Branch)
  2. Name it based on what you're trying (e.g., "add-priority-feature")
  3. Make your changes in this branch
  4. Test thoroughly
  5. If it works: Merge back to main
  6. If it doesn't: Switch back to main branch, delete experimental branch

Workflow 3: Sharing Your Work

  1. Commit all your changes
  2. Publish to GitHub (if not already published)
  3. Add a README.md file explaining what your tool does
  4. Share the GitHub link with colleagues
  5. They can download it, modify it, and share improvements back

Ready to Dive Deeper?

Continue Learning with Our Git Tutor

The Git Tutor provides comprehensive, interactive lessons on Git concepts and workflows specifically designed for clinical tool development.

Explore Git Tutor →

High-Quality External Resources

GitHub Official Resources

Git Fundamentals

Recommended Learning Path

  1. Complete this tutorial with GitHub Desktop
  2. Jump in! See one, do one, teach one!
  3. Watch the GitHub Desktop introduction video
  4. Read chapters 1-3 of Pro Git for deeper understanding
  5. Try the Learn Git Branching interactive tutorial
  6. Explore our Git Tutor for clinical-specific workflows

You're Ready to Build

With AI for code generation and Git for version control, you have everything you need to build custom tools for your practice. Start small, experiment fearlessly, and iterate based on what works.

Support Open Source Clinical AI

All resources are free at this time thanks to your generous support. Consider contributing prompts or supporting development.

Share Your Prompts Support Development Subscribe to Newsletter