Guide / Push & deploy / Start Step 0 / 13 0%

Part three · in Claude Code · Step 5 of 13

Check Claude Code is
in the right folder

Claude can only upload the project it is looking at. Ten seconds now, before you paste anything consequential. Ask it, in the chat:

Paste this into Claude Code 
Which folder are you working in right now?

Claude answers with a path — something like /Users/you/personal-site. Read the end of it: it should be personal-site. That is the entire check.

If it names anything else — a folder above yours, a different project, or a second copy of the kit you are not working in — open your personal-site folder in Claude Code and ask again.

If you have more than one copy

Read the whole path, not just the last word. Every copy of this project contains the same files, so a file list cannot tell them apart — only the path can. Make sure it is the copy you have actually been editing.

Confirm before continuing

Step 6 makes Claude confirm this again before it touches anything. This is the cheap version you can do yourself first.

Part three · in Claude Code · Step 6 of 13

Send your
project up

You will not type a single Git command. Claude runs them and you approve each one.

Paste this into Claude Code 
Please put my personal-site project onto GitHub for me. I have never
used a terminal, so run all the commands yourself and tell me in plain
language what each one does before you run it.

1. Confirm the folder you are in is my personal-site project — it
   should have index.html, knowledge/ and package.json in it. Tell me
   the folder path before you go any further.

2. Find my GitHub username using gh, then check I already have a
   repository called personal-site and that it is private. If it is
   missing, or if it is public, stop and tell me. Do not create one
   and do not change its settings.

3. Before you save or upload anything, show me the exact list of files
   that would go up, and confirm in writing that no .env or .env.local
   file is in that list. My Parley API key lives in those files and it
   must never leave my laptop. If one shows up, stop and tell me.

4. Once you have confirmed that, save my files and upload them to the
   personal-site repository on the main branch.

5. Check it worked: list what is now on GitHub, confirm the repository
   is still private, and confirm no .env file is there. Then give me
   the link to it.

Do not force anything, do not delete anything, and do not edit my
knowledge/ folder. If a step fails, stop and explain it rather than
trying a different way around it.
You will be asked to approve things

Claude asks permission before each command. Read the one-line explanation, then allow it. This is clicking a button in the chat — you are still not using the terminal.

If a .env file did go up, stop

That file holds your Parley API key, and it is now in your repository's history. Tell your instructor before doing anything else. The key has to be replaced — deleting the file is not enough, because the old copy stays in the history.

If part three went wrong
Claude says the upload was rejected
Your repository was not empty — usually one of the three boxes in step 2. Ask Claude to show you what is already on GitHub, then tell your instructor before letting it fix anything.
Claude cannot find a repository called personal-site
Either part one did not finish, or you named it something else. Check the name on GitHub and tell Claude the name you actually used.
Claude asks you for a password or a token
Something in part two did not finish. Do not paste anything. Say "part two may not have completed, please check gh auth status" and let Claude sort it out.
Claude says it is in the wrong folder
Open your personal-site folder in Claude Code, then go back to step 5.

Confirm all three before continuing

This is the one mistake in the whole guide that cannot be undone. Read Claude's list before you tick.