Forking creates your own copy of the repo under your GitHub account.
- Go to the workshop repository link shared by your instructor
- Click the Fork button (top right corner)
- GitHub will create a copy at
github.com/YOUR_USERNAME/repo-name
Cloning downloads the repo to your computer so you can work on it.
git clone https://github.com/YOUR_USERNAME/repo-name.git
cd repo-nameNever work directly on main. Create a branch for your changes.
git checkout -b your-name-contributionExample: git checkout - aryan_daga
Add your file or edit what's needed. For example, creating a file:
touch kachao.pygit add .
git commit -m "Solved w"A good commit message is short and describes what you did.
| Bad | Good |
|---|---|
fixed stuff |
Fix: resolve merge conflict in index.md |
asdfgh |
Add: Readme , API_setup.py |
changes |
Update: correct typo in README |
idk |
Remove: delete duplicate entry in contributors list |
final |
Docs: add setup instructions to README |
last commit i promise |
Fix: remove console.log statements |
okay THIS is the last one |
Fix: actually fix the bug this time |
solved world hunger |
Add: working login form validation |
why is nothing working??? |
Debug: investigate auth token expiry issue |
last ver 1.23.45 FINAL FINAL |
Release: v1.2.0 stable |
my code works dont touch |
Refactor: clean up redundant functions |
god please let this work |
Fix: correct API endpoint URL |
A good commit message completes the sentence: "If applied, this commit will..."
- "If applied, this commit will Add readme file"
- "If applied, this commit will solved world hunger"
If your commit message is a cry for help, it's time to rethink it.
git push origin your-name-contribution- Go to your forked repo on GitHub
- You'll see a "Compare & pull request" button — click it
- Add a short title and description of what you did
- Click "Create Pull Request"
The workshop organizer will review and merge it!
| Command | What it does |
|---|---|
git clone <url> |
Download the repo |
git checkout -b <name> |
Create a new branch |
git add . |
Stage all changes |
git commit -m "message" |
Save a snapshot |
git push origin <branch> |
Upload to GitHub |
- Don't push directly to
main - Don't forget to branch before making changes
- Always pull the latest changes if working over multiple days:
git pull upstream mainYou have already forked this repository and been assigned a personal branch (named after you). All future work must be submitted to that branch. Do not fork the repository again.
Before starting any new work, make sure your fork is up to date with the main repository.
- Go to your fork on GitHub (e.g.
github.com/your-username/repo-name) - Click the "Sync fork" button near the top of the file list
- Click "Update branch" to confirm
Open your terminal inside your local project folder and run:
git checkout main
git pull origin mainReplace your-name with your actual assigned branch name:
git checkout your-nameNot sure of your branch name? Run
git branch -ato list all available branches.
This keeps your branch up to date before you add new work:
git merge mainResolve any conflicts if prompted, then continue.
Once you've completed an exercise or made changes:
git add .
git commit -m "Add: brief description of your work"
git push origin your-name- Go to your fork on GitHub
- Click "Compare & pull request"
- Ensure:
- Base repository → original workshop repository
- Base branch → your assigned branch (
your-name) - Compare branch → your branch from your fork
- Click "Create pull request"
- 🚫 Do NOT open a Pull Request into
main - 🚫 Do NOT create new branches
- ✅ Always push to and PR into your own assigned branch
If you're unsure which branch is yours, check with your instructor before submitting.