Do this once by hand before you let an agent do it. Not because the manual way is better — because when the agent does something strange in week 7, you need to know what it was supposed to do.
The task, both times: add your own name to the team table
in README.md. It is one line. The point is the loop around
it, not the change.
Before either route
- Accept the invitation to your repository. It is in your email and in your GitHub notifications. Until you accept, nothing you do can be pushed.
-
Tell git who you are. If the email on your commits is not
on your GitHub account, GitHub cannot tell the commit is yours, and work
it cannot see does not count towards your individual mark. The steps are
in
docs/setup.mdin your own repository.
Route A — by hand, with GitHub Desktop
The full version of this, with screenshots of every button, is on publishing from your repository. In short:
- Clone the team repository so it is a folder on your laptop.
- Create a branch. Name it after what you are doing:
add-fatima-to-readme. - Edit
README.mdin any editor. Add your name to the table. - Commit with a message that says what changed:
docs(readme): add Fatima to the team table. - Publish the branch, then open a pull request. This change has no story, so in the Closes line write
No issue — first change. - Ask a teammate to review it. They open Files changed › Review changes, write what they checked, and choose Approve.
- The reviewer merges — never the author. Your change is now part of
main.
You cannot push straight to main — GitHub refuses it.
Every change goes through a branch, a pull request and somebody else's
approval. This rule is set on every team repository. It is not a mistake on
your laptop.
Route B — with Antigravity
Open the same folder in Antigravity. Everything below happens in the chat panel, with the repository open.
1. Tell it what it is looking at
Your repository contains a file called AGENTS.md. Antigravity
reads it, and it already says how this course works: the commit format, the
comment rules, the fact that it may commit but must not push, merge, tag or
open pull requests. You do not need to repeat any of that.
2. Ask for the change
Add me to the team table in README.md. My name is Fatima and my
standing role is Client Lead.
Make a branch named after the change first. Commit with a message in
the form the AGENTS.md file describes. Do not push.3. Read what it did, before anything else
- Which files did it touch? It should be one. If it “tidied” something else, undo that.
- Is the branch name sensible, and are you on it?
- Does the commit message carry the right form?
4. Push, and open the pull request yourself
Push it yourself — Publish branch in GitHub Desktop, or the source-control panel in Antigravity, not the chat — then open the pull request on GitHub. Fill in the template, including the AI-Assisted line:
AI-Assisted: Antigravity / wrote the table row and the commit message /
I fixed the role, which it guessed wrongThen the same as Route A: a teammate reviews, and the reviewer merges.
What the agent must never do for you: open the pull request, approve it, merge it, or create a phase tag. Those are the acts the marks are read from. An agent doing them is the one thing that makes a repository unreadable as evidence of who did what.
What to install
One list, kept in one place: the setup guide, Part 1. It covers Windows and macOS, in the order they must be installed — Git for Windows first on a Windows laptop, then Antigravity, then GitHub Desktop and Chrome — and what to do when an installer refuses.
If your laptop cannot run Antigravity, say so. There is a browser-only route through the whole course with the same deliverables and the same marks.
See it finished
The worked example is a real repository with a finished Phase 1 in it — including one pull request that was written, reviewed and merged exactly this way.