Your computer and GitHub
Until now your repository has lived only on your computer. If your laptop breaks, the history goes with it. In this lesson you put a copy on GitHub.
A copy of your repository somewhere else is called a remote. Your computer and GitHub each hold the whole history, and you keep them in step with two commands:
git pushsends your new commits to GitHub.git pullbrings new commits from GitHub to your computer (Lesson 9).
Your repository and its copy on GitHub. On your computer, the remote is known by a short name,
origin. git push sends the commits GitHub does not have yet. origin/main is your computer’s
note of where main is on GitHub.
Create an empty repository on GitHub
- Go to github.com and sign in. In the upper-right corner, click +, then New repository.
- Owner is already you. As the Repository name, type
my-page. - Leave the description empty, or write one, for example “My first web page”.
- Choose Public. Lesson 8 needs it: free accounts can only publish web pages from public repositories.
- Leave the options below as they are: Add README set to Off, no
.gitignore, no licence. Your project already has a history. With any of these, GitHub would start a separate one, and refuse your first push. - Click Create repository.
What to fill in on GitHub’s “Create a new repository” page (a simplified sketch; the real page has
a few more options). Name it my-page, make it public, leave the README off, and create it.
GitHub shows a page with “Quick setup” at the top, and your new repository’s address. Make sure
HTTPS is selected, and copy the address with the copy icon to its right. It looks like
https://github.com/your-username/my-page.git. Below it, GitHub lists some commands for people
who have done this before. You do not need them: this lesson takes you through the ones you need,
one at a time. Keep the page open.
Public means public. Anyone can see everything you push to a public repository, including its whole history. Never put passwords, keys or private documents in it.
Connect your repository to GitHub
Open my-page in VS Code (File > Open Recent) and open a terminal. Tell your repository
about its new remote: type git remote add origin (with a space at the end), paste the address
you copied (with the keys from Lesson 2: Ctrl+V,
Ctrl+Shift+V on Linux, Cmd+V on a Mac), and
press Enter. The box has no Copy button, because the address must contain your own
username:
$ git remote add origin https://github.com/your-username/my-page.gitgit remote add gives the address a short name. origin is the name everyone uses for “the main
copy on GitHub”. Check it:
$ git remote -vorigin https://github.com/your-username/my-page.git (fetch)
origin https://github.com/your-username/my-page.git (push)The same address is used to get commits (fetch) and to send them (push).
If something went wrong
error: remote origin already exists. You have already added it. Check the address with
git remote -v. If it is wrong, fix it with
git remote set-url origin https://github.com/your-username/my-page.git, with your own address.
Send your commits: git push
The first time you push, Git has to check that you are allowed to write to this repository, so it asks you to sign in to GitHub. Read your system’s tab first, then type the command. While you sign in, the terminal waits; that is normal.
A window from Git Credential Manager opens, called “Connect to GitHub”. Click Sign in with your browser. GitHub opens in your browser: sign in if asked, and click the green button to authorise Git Credential Manager. When the browser says you are signed in, go back to VS Code. Git remembers the sign-in, so you only do this once.
If nothing seems to happen, the window may be hidden behind VS Code: look for it on the taskbar. If VS Code says instead “The extension ‘GitHub’ wants to sign in using GitHub”, click Allow and continue as on a Mac.
VS Code shows a message: “The extension ‘GitHub’ wants to sign in using GitHub.” Click Allow. Your browser opens GitHub: sign in if asked, and click the green button to authorise Visual Studio Code. If the browser asks whether to open VS Code, say yes. macOS keeps the sign-in in its keychain, so you only do this once.
If no message appears and the push finishes, you were already signed in.
VS Code shows a message: “The extension ‘GitHub’ wants to sign in using GitHub.” Click Allow. Your browser opens GitHub: sign in if asked, and click the green button to authorise Visual Studio Code. If the browser asks whether to open VS Code, say yes. VS Code remembers the sign-in.
If VS Code warns that “An OS keyring couldn’t be identified”, click Use weaker encryption. If no message appears and the push finishes, you were already signed in.
Now type this command. It means “send my main branch to origin”:
$ git push -u origin mainEnumerating objects: 29, done.
Counting objects: 100% (29/29), done.
Delta compression using up to 8 threads
Compressing objects: 100% (27/27), done.
Writing objects: 100% (29/29), 2.96 KiB | 1.48 MiB/s, done.
Total 29 (delta 11), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Resolving deltas: 100% (11/11), done.
To https://github.com/your-username/my-page.git
* [new branch] main -> main
branch 'main' set up to track 'origin/main'.When you are signed in, the push finishes with the answer above. What it means:
- The first lines count and pack up your commits (“objects” are the pieces Git stores) and send them. Your numbers will differ.
To https://github.com/...is where they went.* [new branch] main -> main: GitHub now has amainbranch too.branch 'main' set up to track 'origin/main': this is what-udid.origin/mainis your computer’s note of wheremainis on GitHub; Git updates it whenever it talks to GitHub. “Track” means that yourmainis now paired with it, so a plaingit push(and, later,git pull) knows where to go.
If something went wrong
A box at the top of VS Code, or the terminal, asks for a username or password. The browser
sign-in did not happen, perhaps because you clicked Cancel. Press Esc (in the
terminal, Ctrl+C), run git push -u origin main again and click Allow.
If the terminal asks again, close it (bin icon), open a new one with Terminal > New
Terminal, and push again. Never type your GitHub password there: GitHub refuses it with
Support for password authentication was removed. If you are not using VS Code’s terminal, see
“Signing in from another terminal” below.
Repository not found. The address is wrong (does it say your-username instead of your own
username?), or the repository does not exist. Compare git remote -v with the address on GitHub,
and fix it with git remote set-url (see above).
Permission to your-username/my-page.git denied to ..., or The requested URL returned error: 403. Git signed in as another GitHub account, the one named after “denied to”. Remove the saved
sign-in: on Windows, in Credential Manager (search for it in the Start menu), under Windows
Credentials, remove the entry for git:https://github.com; on macOS, in the Keychain Access
app, delete the entry for github.com; in VS Code, click the Accounts icon at the bottom of
the bar on the left and sign out. Then push again and sign in as yourself.
error: src refspec main does not match any. You have no branch called main. Run
git branch: if your branch is called master, rename it with git branch -M main and push
again.
! [rejected] main -> main (fetch first). The repository on GitHub is not empty, for example
because Add README was on. Run git pull origin main --allow-unrelated-histories, close the
message tab that opens, then git push -u origin main again. Your project now has GitHub’s
README.md: in “Add a README” below, replace its content with the one shown.
GH007: Your push would publish a private email address. Your commits use your real email
address, and your GitHub settings protect it. Set the private address (Lesson 2, Step 5). Then see
which commits carry your real address: git log --format="%h %ae". If only the newest one does,
run git commit --amend --reset-author --no-edit and push again. If older ones do too, amending
the newest is not enough: GitHub checks only the newest commit, so the push would go through and
publish your address in the older ones. Rewriting old commits is an advanced job. If you are happy
for that address to be public in those commits, untick Block command line pushes that expose my
email in GitHub’s email settings, push, and tick it again.
See your project on GitHub
Reload your repository’s page, https://github.com/your-username/my-page. You see:
- the list of your files,
index.htmlandstyle.css; - above the list, your latest commit’s message and the number of commits. Click the number to see
your whole history, as in
git log; - click
index.htmlto read it on GitHub.
GitHub also suggests Add a README. Do not click it: you will add one from your computer in the next step.
Everything you committed on your computer is now on GitHub too, history and all.
Add a README
A README is a file that explains a project. GitHub shows it below the file list, on the
repository’s front page. Its name is usually README.md; the .md means it is written in
Markdown, plain text with a few symbols for formatting: # makes a heading.
Create README.md in VS Code, next to index.html:
# My page My first project with Git and GitHub: a small personal web page.$ git add README.md$ git commit -m "Add a README"[main 315e479] Add a README
1 file changed, 3 insertions(+)
create mode 100644 README.mdBefore you push, look at what git status says now:
$ git statusOn branch main
Your branch is ahead of 'origin/main' by 1 commit.
(use "git push" to publish your local commits)
nothing to commit, working tree clean“Ahead of ‘origin/main’ by 1 commit”: as far as your computer knows, GitHub does not have one of
your commits yet. Push it. Because of the -u earlier, plain git push is enough:
$ git pushEnumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 408 bytes | 408.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0 (from 0)
To https://github.com/your-username/my-page.git
10984c7..315e479 main -> main$ git statusOn branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean10984c7..315e479 main -> main says GitHub’s main moved from your old newest commit to the new
one. “Up to date with ‘origin/main’”: as far as your computer knows, GitHub has the same commits
as you. Reload the page on GitHub: your README appears below the files.
VS Code’s status bar, at the bottom of the window, shows the same thing with arrows and numbers. In this series, push and pull in the terminal, not with VS Code’s Sync Changes button, so that what you see matches the lessons.
Commit often, push when you finish. A commit is saved on your computer only. It is backed up, and visible to others, only once you push it.
Signing in from another terminal
If you type commands in a terminal outside VS Code, VS Code cannot sign you in. The simplest answer is to use VS Code’s terminal, as in the rest of this series. You may not need this section at all:
- On Windows, Git Credential Manager signs you in from every terminal.
- On a Mac, the sign-in you made in VS Code’s terminal is kept in the keychain, so it works in the Terminal app too.
Otherwise, mostly on Linux, install GitHub CLI as described at
github.com/cli/cli. (On a Mac, brew install gh works
only if you have Homebrew; if the terminal says command not found: brew, use the macOS installer
from that page instead.) Then run:
$ gh auth login? Where do you use GitHub? GitHub.com
? What is your preferred protocol for Git operations on this host? HTTPS
? Authenticate Git with your GitHub credentials? Yes
? How would you like to authenticate GitHub CLI? Login with a web browser
! First copy your one-time code: 1A2B-3C4D
Press Enter to open https://github.com/login/device in your browser...
✓ Authentication complete.
✓ Logged in as your-usernameChoose the answers shown, using the arrow keys and Enter. gh may print a few more lines
than these; what matters is the last one, ✓ Logged in as your-username. When your browser
opens, type the eight-character code shown in your terminal, then click Continue and the green
button to authorise GitHub CLI. Typing the code is easier than copying it: in a terminal,
Ctrl+C cancels the command. After that, Git uses this sign-in for every
push.
What you learned
- A remote is another copy of your repository.
originis the usual name for the one on GitHub. - Create the GitHub repository empty when you already have a project.
git remote add origin URLconnects the two, once.git push -u origin mainsendsmainthe first time; after that,git pushis enough.git statussays whether you are ahead of GitHub (you have commits to push) or up to date.- GitHub needs a sign-in through the browser, not your password, the first time you push.
| Command | What it does |
|---|---|
git remote add origin URL |
Connects your repository to a remote called origin |
git remote -v |
Shows your remotes and their addresses |
git push -u origin main |
Sends main to GitHub and remembers where it goes |
git push |
Sends your new commits to GitHub |
Check yourself
origin?origin is only a nickname for an address, set by git remote add. It is the usual name, not a rule.git status says “Your branch is ahead of ‘origin/main’ by 2 commits”. What does it mean?git pull (Lesson 9) brings them.