How to use GitHub for project collaboration | Usage Guides | PeopleEdge | PeopleEdge

Guide · Cursor essentials

How to use GitHub for project collaboration

1 Chapters22 minProgress is saved in this browser only

Guide progress0/11

Chapter 1

Use GitHub so the team can edit together

Step 01

Why zip and Drive fail

Introduction

After localhost works, a zip or a Google Drive folder still cannot let several people edit a programming project at the same time. GitHub is the shared folder built for that work.

Key takeaways

A zip or Drive folder is not team editing for code
Programming files are not a Google Doc — you cannot see the whole program at a glance
GitHub is the shared project folder for programmers: invite, versions, and merge without frying the app

Look at the stills. They walk through why a zip hand-off and Google Drive both fail for a programming project, then why GitHub exists: invite teammates, keep versions, and combine work without breaking the program.

Cantonese voice guide

0:000:00

Try it

Name one reason zip or Drive cannot replace GitHub for code.

6 minOfficial source

Step 02

GitHub keywords you need first

Introduction

Before you use GitHub, learn these seven words so you do not mix them up: Repo, Commit, Branch, Push, Pull, Pull Request, and Merge. The video on the still explains each one.

Key takeaways

Repo: the official shared project folder on GitHub
Commit: a snapshot of the whole project plus a short note — save is not a commit
Branch: a draft line so work does not land on official main yet
Push: upload your commits to GitHub — push is not merge
Pull: download commits that are on GitHub but not on this computer
Pull Request: ask to put your branch into main
Merge: the approved branch becomes part of official main

Read the seven words, then open the reference video for a longer walkthrough. Keep the pairs straight: save is not a commit, push is not a Pull Request, and pull is not merge.

Cantonese voice guide

0:000:00

Try it

Open the reference video, then say what Repo, Commit, and Pull Request each mean.

3 minOfficial source

Step 03

Open a GitHub account

Introduction

GitHub is the website that holds the shared project. You need an account before Cursor can connect and before teammates can join a private repo.

Key takeaways

You need a GitHub account before the team can share a project
Watch the sign-in / sign-up clip, then continue

Open GitHub sign-in or sign-up in the browser. Use https://github.com/login if you already have an account, or https://github.com/signup if you do not. Type the password and any 2FA yourself. Never paste a password into chat.

Navigation

Browser → github.com/login or github.com/signup

Cantonese voice guide

0:000:00

Try it

https://github.com/signup

1 minOfficial sourceInterface may change with product updates

Step 04

Create a repo and name it

Introduction

Open a new GitHub repository for the team. You choose the name. Visibility must stay Private so the whole internet cannot read the homework.

Key takeaways

GitHub → + → New repository
Name with letters, numbers, hyphens; no spaces; prefer lowercase
team-notes is only an example name — Visibility must be Private

On GitHub, open the + menu at the top right and choose New repository. Name the repo with letters, numbers, and hyphens only — no spaces; prefer lowercase. Example name only: team-notes. The name in the screenshot is just one example. Set Visibility to Private, then choose Create repository. Remember the HTTPS URL GitHub shows you.

Navigation

GitHub → + → New repository → name → Private → Create repository

Cantonese voice guide

0:000:00

Try it

Create one Private repo. Use letters, numbers, and hyphens — no spaces. Copy the HTTPS URL.

https://github.com/new

1 minOfficial sourceInterface may change with product updates

Step 05

Share the repo with teammates

Introduction

A private repo is invisible to teammates until you invite them. The link alone is not enough. They must Accept the invitation before they can clone.

Key takeaways

A private repo link is useless until they are invited
Settings → Access → Collaborators → Add to repository
They must Accept the email or GitHub notification

Open the repo Settings tab, then Access → Collaborators. Add the teammate by GitHub username or email and choose Add to repository. They receive an invitation email or GitHub notification and must Accept before they can open the project.

Navigation

Repo → Settings → Access → Collaborators

Cantonese voice guide

0:000:00

2 minOfficial sourceInterface may change with product updates

Step 06

Clone the repo in Cursor

Introduction

After the invitation is accepted, copy the GitHub repo onto this computer and open that folder in Cursor. That copy step is called clone. Do it once at the start — not every work session.

Key takeaways

Clone copies the repo onto this computer and opens the folder
Do this after the teammate Accepts
Paste the clone prompt in a new Agent chat — do not type git commands yourself

Open a new Cursor Agent chat (not this guide). Paste the clone prompt and attach or type the repo HTTPS URL in place of [Attach the link of the Repo]. The Agent saves the folder to this computer and opens it. You do not run git commands yourself.

Cantonese voice guide

0:000:00

Try it

Open a new Agent chat and paste this prompt. Attach or type the repo HTTPS URL, then send it:\nPlease clone this GitHub repo [Attach the link of the Repo] onto this computer.

Please clone this GitHub repo [Attach the link of the Repo] onto this computer.

1 minOfficial sourceInterface may change with product updates

Step 07

Open the project and start localhost

Introduction

After clone, start the local app if the project has a dev script. When the Agent gives you a localhost URL, the app is running and you can begin the homework.

Key takeaways

Start the local app from a new Agent chat
Wait until the Agent gives a localhost URL
You can edit only after the app is running

Open a new Cursor Agent chat (not this guide). Paste the start-app prompt. The Agent looks for a dev script, starts the app, and tells you the localhost URL. Open that URL in the browser to confirm the page is up.

Cantonese voice guide

0:000:00

Try it

Open a new Agent chat and paste this prompt. When the Agent replies, open the localhost URL it gives you.

Start the local app if there is a dev script.
Tell me the localhost URL when it is running.

2 minOfficial sourceInterface may change with product updates

Step 08

Pull the latest from GitHub

Introduction

The repo is already on this computer. Before you edit, pull so this machine matches GitHub. Clone is only for the first copy — later sessions use pull.

Key takeaways

Do not clone again every work session
Pull brings GitHub updates this computer does not have yet
Paste the pull prompt in a new Agent chat — do not run git commands yourself

Open a new Cursor Agent chat (not this guide). Paste the pull prompt. The Agent syncs the latest from GitHub into this local repo. You do not run git commands yourself.

Cantonese voice guide

0:000:00

Try it

Open a new Agent chat and paste this prompt. Wait until the Agent says this computer has the latest from GitHub.

Pull or sync the latest changes from GitHub into this local repo.

1 minOfficial sourceInterface may change with product updates

Step 09

Push finished work and open a PR

Introduction

Your homework changes are already finished and saved. One Agent prompt opens a draft branch, records a commit, pushes that branch, and opens a Pull Request. Then open the PR link on GitHub. If there is no conflict, you can Merge.

Key takeaways

One prompt: new branch → commit → push the draft → open a PR
Push is not merge; the PR URL is where teammates look
Open the PR link. Conflict blocks Merge; no conflict: you can click Merge

Finish your file changes and save. Open a new Agent chat (not this guide) and paste the branch / commit / push / PR prompt. The Agent must not edit your homework, must not push to main, and must not merge. When it finishes, keep the PR URL. Open that GitHub link. GitHub checks whether your draft conflicts with the official file. If there is a conflict, GitHub will not let you merge. If there is no conflict, you can click Merge.

Cantonese voice guide

0:000:00

Try it

After you save real homework, open a new Agent chat and paste this prompt. Then open the PR URL. If GitHub shows no conflict, Merge.

My work changes are already finished and saved.
Do not edit my files. Do not invent a new file or a practice line.

1) If I am still on the official line, create and switch to a new branch.
If I already gave a branch name, use that. If I did not, choose a short valid name
(letters, numbers, hyphens, slashes; example shape only: feature/add-my-intro).
Tell me the branch name you chose.

2) Commit my existing changes on that branch.
Do not ask me to click Source Control, stage, Commit, or Sync Changes.
If there is nothing to commit, say so and stop. Do not create a change just to commit.
Use a short commit message that matches what actually changed.

3) Push this branch to GitHub. Do not push to main. Do not merge.

4) Open a Pull Request:
- base: main
- compare: the branch you just pushed
Write a title and two lines of what and why.
Do not merge yet.

Never ask for my password.
I will not run git commands myself.
When done, tell me the branch name, the commit message, and the PR URL.

1 minOfficial sourceInterface may change with product updates

Step 10

Pull the merged work onto this computer

Introduction

After Merge, the official project on GitHub has the new work. This computer still has the old copy until you pull. Switch to main and pull so you have the merged work locally.

Key takeaways

Merge updates GitHub, not this computer
Switch to main and pull after merge
Paste the prompt in a new Agent chat — do not click Sync Changes

After someone Merges on GitHub, open a new Cursor Agent chat (not this guide). Paste the pull-main prompt. The Agent switches this repo to main and syncs the latest from GitHub. Do not click Sync Changes. You do not run git commands yourself. When the Agent finishes, this computer has the merged work.

Navigation

New Agent chat → paste the pull-main prompt

Cantonese voice guide

0:000:00

Try it

Open a new Agent chat and paste this prompt. Wait until the Agent says you have the merged work locally.

Switch this repo to main and pull or sync the latest from GitHub.
Do not ask me to click Sync Changes.
I will not run git commands myself.
When done, tell me I have the merged work locally.

2 minOfficial sourceInterface may change with product updates

Step 11

The full GitHub collaboration loop

Introduction

Say the whole path once. First day: GitHub account, connect Cursor, Private repo, invite teammates, wait for Accept, then clone. A private link does nothing until they Accept. Every later change is pull, branch, edit and save, commit, push, PR, merge, then pull again.

Key takeaways

First time: account → connect Cursor → Private repo → invite → Accept → clone
A private link is useless until they Accept
Later: pull → branch → edit → save → commit → push → PR → merge → pull again

This is the recap, not a new action. First-time setup: open a GitHub account, connect Cursor, create a Private repo, invite teammates, wait for Accept, then clone. Without an invite, the link will not open. After that, each change starts by pulling the latest from GitHub. Open a new branch, edit and save, commit that moment, push the branch, and open a PR. After someone reviews and Merges, everyone pulls again so this computer has the official project.

Cantonese voice guide

0:000:00

Try it

Say the first-time path, then the later loop: pull, branch, save, commit, push, PR, merge, pull again.

2 minOfficial source