Ops: publish and share
- Role
- Ops
- Outcome
- Your site live, and the link shared; your feedback sent while it goes live
- Time box
- 8 minutes
Ops publishes your site. It saves your changes in a commit (a saved version with a short message), sends it to GitHub with a push, and tells you your live address.
Get ready 2:00 min
Ops publishes your site to GitHub. One thing before you start:
- Nothing private in your folder. Everything in your
YOUR-REPOfolder can go into your public repo, and it stays there even after you delete it. Ops lists every file before it publishes, and you read the list.
Work with Ops 4:00 min
Ops leads you through this Block in the chat and says when it is done. Read this part first, then start Ops at its end, under Now start Ops. Keep this page open next to the chat.
Check the file list
Ops lists the files that changed (git status) and says what each one is. Every file should be in site/, or be design/brief.md or docs/spec.md. Your photo belongs there only as the small copy in site/assets/.
Ops names every file that does not belong. Move each one out of the folder, for example to your Documents folder:
In Finder, press Cmd+Shift+H (or menu Go → Home), then open YOUR-REPO. Drag the file onto Documents in the sidebar.
In File Explorer, click into the address bar, type %USERPROFILE%\YOUR-REPO and press Enter. Drag the file onto Documents in the left pane.
In Files, open Home, then YOUR-REPO. Drag the file onto Documents in the sidebar.
Then tell Ops you moved it. It checks the list again.
Say yes to publish
Ops runs the Check once more and asks: "Shall I publish these changes? Say yes." Say yes. It makes the commit and pushes it to GitHub. If it asks to run two git config commands, allow them.
If GitHub asks you to sign in
The Setup line signed you in to GitHub, so the push needs no password. Ops reports could not read Username, or the push asks for a username or password? Do not type your GitHub password.
- Open a second terminal window and paste the line from Setup again. It only does what is missing: here, the sign-in to GitHub in your browser.
- Back in the Antigravity CLI, tell Ops: "I signed in. Please push again."
Now start Ops
In the Antigravity CLI, type /clear and press Enter. It resets the context window, so this Role starts in a fresh chat.
Then type:
Agent chat
Start the Ops step.
Ops then publishes your site and waits until it is live: Live and share below shows what you see.
Live and share 2:00 min
Wait until it is live
Ops waits until the new version is online, usually within a minute:
What you see (example)
Your site's address: https://luca-bianchi.github.io/portfolio/
An older version is online; the new one is on its way. Looking again in 10 seconds…
Your site is live. Open https://luca-bianchi.github.io/portfolio/ in Chrome and share the link.
It says that GitHub Pages is probably off? Repeat the Pages setting from Setup (step 3 of Your repo by hand), then tell Ops done.
Share your link
- Open your address in Chrome and on your phone:
https://YOUR-USERNAME.github.io/YOUR-REPO/. - Show it to your neighbour, and look at theirs.
- Add it to the room's gallery: paste your address and click Add my site.
It appears on the Instructor's slides with the rest of the room. Changed your address? Send it again: the new one replaces the old one.
If something goes wrong
Ask your agent first. In a fresh chat, type the question below: it reads your repo and tells you what is done and what comes next. Got an error message? Paste it into the chat.
Agent chat
Where am I?
"Permission denied" or "403" when pushing
Cause: you are signed in to GitHub with another account than the one that owns the repo.
Fix: raise your hand; the Instructor helps you switch accounts.
"'git' is not recognized", "command not found: git", "not a git repository", or a window about developer tools
Cause: Git is missing on your laptop, or you installed it after the Install script had copied your repo.
Fix, if Git is installed now: run your line from Run the Install script again, in a fresh terminal. It connects your YOUR-REPO folder to Git and keeps your files. Then start a fresh chat and type Start the Ops step.
Fix, if you have no administrator rights: publish in the browser.
- On github.com, open your repo
YOUR-REPO. Click Add file → Upload files. - Open your
YOUR-REPOfolder on your laptop, as in Check the file list. Drag the wholesitefolder onto the GitHub page and wait until the files are listed. - Click Commit changes. When the newest Deploy to GitHub Pages run in the Actions tab has a green tick, open your address.
"rejected" and "fetch first"
Cause: your repo on GitHub has a change your laptop does not have yet, for example an edit on github.com.
Fix: Ops fetches the change and pushes again. If it reports a conflict, ask the Instructor.
The live address shows an older version
Fix: wait a minute and reload. In your repo on GitHub, the tab Actions shows the newest Deploy to GitHub Pages run; it should get a green tick.
Fell behind?
The Ops Block's time is up and your site is not live yet?
- Ops still working? Keep its chat going: no checkpoint can publish for you.
- Your page is broken or missing? Stop Ops, run the checkpoint below, then type
Start the Ops step.in a fresh chat.
The Ops checkpoint is the same as QA's: it keeps your own content file, design brief and spec, and writes your legal page if you have none. It also resets your page to a ready-made one in the colours and fonts of your brief: what your own Developer and QA built is lost.
- The agent is still working? Press Esc in the Antigravity CLI to stop it.
- Open a second terminal window, next to the Antigravity CLI. Type
cd YOUR-REPOand press Enter. Then paste this command (Cmd+V on a Mac, Ctrl+V on Windows, Ctrl+Shift+V on Linux) and press Enter:
Terminal · same on Mac, Windows and Linux
node tools/checkpoint.mjs ops
Use the Block that has just ended, not the one that starts now.
It lists what it kept and what it changed. Nothing to change means you were already there.
Or start a fresh chat and let the agent run it:
Agent chat
Catch me up: the room just finished the Ops block.