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

Push your project to GitHub

GitHub holds an online copy of your saved source files. Cloudflare will use that copy to publish the site.

In GitHub Desktop and your browser8 min read & do
By the end of this lesson

Publish a private repository from the existing local project and verify the files reached GitHub.

Let’s do this

  1. 1
    In GitHub Desktop

    Check the selected project and account

    In GitHub Desktop, make sure Current Repository is your website. Sign in through the app’s browser flow if needed. Use GitHub Free; paid Copilot, Codespaces and Actions are not required for this publishing route.

    GitHub: free plan (opens a new tab)
  2. 2
    In GitHub Desktop

    Publish the repository

    Click Publish repository. Give it a simple name such as little-garden. Keep “Keep this code private” selected and choose your personal account. Click Publish Repository. A repository is your online project and its change history.

    GitHub Desktop: publish an existing project (opens a new tab)
  3. 3
    In your browser

    Open the GitHub copy

    Use Repository, then View on GitHub. Confirm the owner, repository name, Private badge and your latest checkpoint. You should see package.json and the source folder. A private code repository can still supply a public Cloudflare website.

  4. 4
    In GitHub Desktop

    Learn the update cycle

    Next time: let the AI edit the local folder, test the change, review Changes in GitHub Desktop, write a summary, commit, then click Push origin. Commit saves locally; Push sends it online. After Cloudflare is connected, pushing main can update the live site.

A message for your AI helper

Help me publish this existing local website repository to my GitHub Free account using GitHub Desktop. Review that secrets and generated files are excluded. Guide me to keep the source private and confirm the online repository and main branch contain the latest working version. Explain the difference between saving a file, committing and pushing. Do not create a second local copy.

What you should see

Your browser shows the private GitHub repository with the same source files and checkpoint as your Mac.

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: free planGitHub Desktop: publish an existing projectVite: public environment variables