In the previous chapter, the project already existed on the server. Here, we start from an empty folder: we initialize Git, then send the project to GitHub.

1. Initialize Git: git init

Create a folder with a first file, then initialize Git inside it:

mkdir git-demo
cd git-demo
echo "test" > test.txt
git init
# Initialized empty Git repository in …/git-demo/.git/

Git creates a hidden .git folder. That’s where it stores the project’s whole history and configuration. Don’t delete it: without it, the folder is no longer a Git repository.

2. Create the repository on GitHub

On GitHub, click New repository:

  • Name: git-demo;
  • Visibility: public or private;
  • README, .gitignore, license: leave them empty, since your project already exists locally.

What’s .gitignore?

Some files must never go to GitHub: local config files, passwords, downloaded dependencies… Just list them in a .gitignore file at the root of the project, and Git will ignore them:

.env.local
/vendor/
/node_modules/

You can edit those files freely on your machine: they’ll never be sent.

Once the repository is created, GitHub shows the commands to run. We add the remote, meaning the address of the remote repository:

git remote add origin https://github.com/<user>/git-demo.git

Check it:

git remote -v
# origin  https://github.com/<user>/git-demo.git (fetch)
# origin  https://github.com/<user>/git-demo.git (push)
  • fetch: the address used to get data;
  • push: the address used to send it.

4. First commit

With the commands from the previous chapter:

git status
git add .
git commit -m "First commit"

5. The default branch

After git init, Git creates a default branch, master here. To work on another branch, you already know how: git checkout -b <name>. In this example, we push straight to master.

GitHub uses main as the default name. To make your new projects start on main: git config --global init.defaultBranch main.

6. First push

git push
# fatal: The current branch master has no upstream branch.

That’s expected: on GitHub, we only created the repository, without any branch. Git gives you the exact command:

git push --set-upstream origin master

Refresh the GitHub page: your file is there, on the master branch. Get into the habit of reading Git’s messages: very often, they tell you exactly what to do.

Recap

CommandRole
git initTurn a folder into a Git repository
.gitignoreList the files Git should ignore
git remote add origin <url>Link the project to a remote repository
git remote -vShow remote repositories
git push --set-upstream origin <branch>First push of a branch

Exercise · Ignore the right files

Your project has a node_modules/ folder, a .env file with passwords and some *.log files. Write the .gitignore.

Show the solution
node_modules/
.env
*.log

A name ending with / means a folder, and * matches any sequence of characters. Then check with git status: those files must no longer show up.

What’s Next

In the next chapter, we discover a command that saves the day when you have to switch tasks urgently: git stash.


This is Chapter 4 of the Git in Practice course. Follow along to learn how to use Git every day and as a team.