Your first commit

The beginner-proof path from “I do not code” to “my code is on GitHub” — with GitHub Copilot helping you, not raw git syntax.

No credit card. No local git commands required for the flagship path. Start in the browser, then choose the route that matches your comfort level.

If this first test already feels bigger than one repository, take the 2-minute diagnostic to choose the most useful institutional next page.

1. Create your GitHub account ↗ source

Start at github.com/signup. A verified email is required before you can create a repository, and enabling 2FA right after sign-up is the smart next step.

⚡

30-second start ↗ source

Go to github.com/signup and create your account. Google and Apple sign-in are supported.

✉️

Verify your email ↗ source

GitHub asks for a verified email before you can create your first repository.

🔐

Turn on 2FA next ↗ source

Do it right after sign-up so your new account starts secure from day one.

2. Create your first repository in the browser ↗ source

This is the zero-install path and the friendliest way to understand what a repository feels like before you touch any tooling.

01

Click the + icon ↗ source

In the top-right corner of GitHub, click the + menu and choose New repository.

02

Give it a short name ↗ source

Pick something simple and memorable such as hello-world, quiz-demo, or campus-faq.

03

Choose visibility ↗ source

Public is fine for demos; private is fine for internal experiments.

04

Turn on Add README ↗ source

That creates the repository with one file already inside, so you can make a first change immediately.

05

Create repository ↗ source

Click Create repository and you are done: GitHub just created your first project space.

Screenshot-style checklist
  1. + New repository
  2. Repository name: hello-world
  3. Description: optional
  4. Visibility: Public or Private
  5. Add README: On
  6. Create repository
Optional 60-second warm-upOpen README.md, click the pencil icon, add one sentence, preview, then commit. That is already a real first change on GitHub before you ask Copilot to do more.
Helpful terms on this page

3. Choose how you want Copilot to help you push code

There is no single “correct” beginner path. Pick the one that matches your confidence today.

🌐

Best for total beginners

I am starting in the browser ↗ source ↗ source

Teaching staff, HR, finance, admin, support teams

Zero install. Copilot can write the code, open the pull request, update the branch, and let you merge everything without local git commands.

  1. Open or create a small issue in the repository, such as “Add a CONTRIBUTING.md file” or “Build a simple quiz page”.
  2. In the right sidebar, open Assignees, choose Copilot, add an optional prompt if useful, then click Assign.
  3. Optional: open the Agents tab and start a second natural-language task to show two agent sessions running in parallel.
  4. When the pull request is ready, request Copilot as a reviewer so Copilot code review comments arrive on the PR.
  5. If you want changes, comment @copilot on the pull request. When you are happy, merge it — and that merge is the push.

Copilot cloud agent must be enabled on the repository. See the plans page

And there it is: your code is on GitHub, entirely through the browser.

⌨️

Best for technical beginners

I am comfortable with a terminal ↗ source ↗ source ↗ source

IT staff, technical researchers, advanced students

Copilot CLI is a strong level-two route when you like plain-language automation but still want the terminal nearby.

Install options
  • npm install -g @github/copilot
  • winget install GitHub.Copilot
  • brew install --cask copilot-cli
  • curl -fsSL https://gh.io/copilot-install | bash
  1. Install Copilot CLI, move into your project folder, and run copilot.
  2. Type /login the first time and follow the prompts to authenticate with your GitHub account.
  3. Confirm that you trust the current directory’s files for AI use when asked.
  4. Then use plain language, for example: “Create a simple HTML quiz page about photosynthesis with 5 questions, then commit and push it to a new branch and open a pull request.”
  5. Review the plan or execution, keep the useful edits, and let Copilot help you finish the branch and PR flow.

Interactive mode is the default. Shift+Tab toggles Plan mode before code is written, and copilot -p "prompt" is the non-interactive route.

And there it is: your code is on GitHub, with Copilot guiding the terminal work instead of raw git memorisation.

🖱️

Best for visual review

I want a graphical interface ↗ source

People who want buttons, diffs, and a visible review step

GitHub Desktop is the bridge option: build with Copilot where you like, then review, commit, and push visually.

  1. Download GitHub Desktop from desktop.github.com and sign in with your GitHub account.
  2. Clone your new repository or open the local project folder you are editing with Copilot elsewhere.
  3. Make your content or code changes with Copilot in the browser or your editor of choice.
  4. Return to GitHub Desktop, review the diff, let Copilot suggest the commit message or description, then click Commit.
  5. Click Push origin and, if needed, open the pull request from GitHub Desktop or github.com.

This path is especially good when you want a clear “look at the diff before it leaves my machine” moment.

And there it is: your code is on GitHub, without living in a terminal.

Helpful terms on this page

4. What next?

Once the first repository exists, the rest gets much easier because every next step has a home.

Was this page helpful?