First App.
Your learning space A little progress, every day
CHAPTER 05Lesson 15 of 20

Save a working version on your Mac

Git keeps named checkpoints of your files. GitHub Desktop lets you review and save those checkpoints with buttons.

In GitHub Desktop8 min read & do
By the end of this lesson

Create a local history and save your first working version before uploading anything.

Let’s do this

  1. 1
    In your AI helper

    Ask the AI to prepare this folder for Git

    Have it check whether Git is already set up. If not, initialise it in the current project folder and add a suitable .gitignore file. That list keeps downloaded tools, generated builds, local data and secret settings out of saved source. It must not remove any existing online connection without asking.

    GitHub: ignore files (opens a new tab)
  2. 2
    In GitHub Desktop

    Add the existing folder to GitHub Desktop

    Open GitHub Desktop. Choose File, then Add Local Repository. Click Choose and select little-garden, the folder containing package.json. Click Add Repository. If it says the folder is not a Git repository, return to the AI for the first step; do not create a second nested website folder.

    GitHub Desktop: add a local repository (opens a new tab)
  3. 3
    In GitHub Desktop

    Review the changes list

    You should see source and setup files. You should not see node_modules, .env, secret keys or a live database export. Ask the AI to review what is about to be saved if you are unsure. A private repository is still not a place for passwords.

  4. 4
    In GitHub Desktop

    Make your first checkpoint

    In the Summary box type “First working website”. Click Commit to main, or the current branch shown. A commit is a named local checkpoint. Look in History to see it. So far it is on your Mac; the next lesson sends it to GitHub.

A message for your AI helper

Prepare this existing website folder for local version history. Check for existing Git setup and preserve any existing remote. If needed, initialise Git here and make a suitable .gitignore for this project. Exclude secrets, downloaded packages, generated builds and local database files. Review the files that would be committed and explain any concerns. Guide me to save “First working website” in GitHub Desktop.

What you should see

GitHub Desktop shows a first checkpoint in History and no secrets or generated tool folders in that checkpoint.

If you get stuck

Go at your own pace. There is no test to pass.

Checked 7 September 2026. Screens can change; the official guides below have the latest steps.

GitHub Desktop: add a local repositoryGitHub: ignore filesGitHub Desktop: publish an existing project