New to git? Follow the steps below to get comfortable making changes to the code base, opening up a pull request (PR), and merging code into the primary branch. Any important git and GitHub terms are in bold with links to the official git reference materials.
Step 0: Install git and create a GitHub account
The first two things you’ll want to do are install git and create a free GitHub account.
Git and GitHub
A quick aside: git and GitHub are not the same thing. Git is an open-source, version control tool created in 2005 by developers working on the Linux operating system; GitHub is a company founded in 2008 that makes tools which integrate with git. You do not need GitHub to use git, but you cannot use GitHub without using git. There are many other alternatives to GitHub, such as GitLab, BitBucket, and “host-your-own” solutions such as gogs and gittea. All of these are referred to in git-speak as “remotes”, and all are completely optional. You do not need to use a remote to use git, but it will make sharing your code with others easier.
Step 1: Create a local git repository
When creating a new project on your local machine using git, you’ll first create a new repository (or often, ‘repo’, for short).
To use git we’ll be using the terminal. If you don’t have much experience with the terminal and basic commands, check out this tutorial (If you don’t want/ need a short history lesson, skip to step three.)
To begin, open up a terminal and move to where you want to place the project on your local machine using the cd (change directory) command. For example, if you have a ‘projects’ folder on your desktop, you’d do something like:
myname:Desktop myname$ cd ~/Desktop
myname:Desktop myname$ mkdir myproject
myname:Desktop myname$ cd myproject/
To initialize a git repository in the root of the folder, run the git init command:
myname:myproject myname$ git init
Initialized empty Git repository in /Users/myname/Desktop/myproject/.git/
Step 2: Add a new file to the repo
Go ahead and add a new file to the project, using any text editor you like or running a touch command. touch newfile.txt just creates and saves a blank file named newfile.txt.
Once you’ve added or modified files in a folder containing a git repo, git will notice that the file exists inside the repo. But, git won’t track the file unless you explicitly tell it to. Git only saves/manages changes to files that it tracks, so we’ll need to send a command to confirm that yes, we want git to track our new file.
myname:myproject myname$ touch myname.txt
myname:myproject myname$ ls
myname.txt
After creating the new file, you can use the git status command to see which files git knows exist.
myname:myproject myname$ git status
On branch main
Initial commit
Untracked files:
(use "git add <file>..." to include in what will be committed)
myname.txt
nothing added to commit but untracked files present (use "git add" to track)
What this basically says is, “Hey, we noticed you created a new file called myname.txt, but unless you use the ‘git add’ command we aren’t going to do anything with it.”
Step 3: Add a file to the staging environment
Add a file to the staging environment using the git add command.
git add .
If you rerun the git status command, you’ll see that git has added the file to the staging environment (notice the “Changes to be committed” line).
myname:myproject myname$ git status
On branch main
Initial commit
Changes to be committed:
(use "git rm --cached <file>..." to unstage)
new file: myname.txt
To reiterate, the file has not yet been added to a commit, but it’s about to be.
Step 4: Create a commit
It’s time to create your first commit!
Run the command git commit -m "Your message about the commit"
myname:myproject myname$ git commit -m "This is my first commit!"
[main (root-commit) b345d9a] This is my first commit!
1 file changed, 1 insertion(+)
create mode 100644 myname.txt
The message at the end of the commit should be something related to what the commit contains - maybe it’s a new feature, maybe it’s a bug fix, maybe it’s just fixing a typo. Don’t put a message like “asdfadsf” or “foobar”. That makes the other people who see your commit sad. Very, very, sad. Commits live forever in a repository (technically you can delete them if you really, really need to but it’s messy), so if you leave a clear explanation of your changes it can be extremely helpful for future programmers (perhaps future you!) who are trying to figure out why some change was made years later.
Step 5: Create a new branch
Now that you’ve made a new commit, let’s try something a little more advanced.
Say you want to make a new feature but are worried about making changes to the main project while developing the feature. This is where git branches come in.
Branches allow you to move back and forth between ‘states’ of a project. Official git docs describe branches this way: ‘A branch in Git is simply a lightweight movable pointer to one of these commits.’ For instance, if you want to add a new page to your website you can create a new branch just for that page without affecting the main part of the project. Once you’re done with the page, you can merge your changes from your branch into the primary branch. When you create a new branch, Git keeps track of which commit your branch ‘branched’ off of, so it knows the history behind all the files.
Let’s say you are on the primary branch and want to create a new branch to develop your web page. Here’s what you’ll do: Run git checkout -b . This command will automatically create a new branch and then ‘check you out’ on it, meaning git will move you to that branch, off of the primary branch.
After running the above command, you can use the git branch command to confirm that your branch was created:
myname:myproject myname$ git branch
main
* my-new-branch
The branch name with the asterisk next to it indicates which branch you’re on at that given time.
A note on branch names By default, every git repository’s first branch is named
main(and is typically used as the primary branch in the project). As part of the tech industry’s general anti-racism work, some groups have begun to use alternate names for the default branch (we are using “primary” in this tutorial, for example). In other documentation and discussions, you may see “main”, or other terms, used to refer to the primary branch. Regardless of the name, just keep in mind that nearly every repository has a primary branch that can be thought of as the official version of the repository. If it’s a website, then the primary branch is the version that users see. If it’s an application, then the primary branch is the version that users download. This isn’t technically necessary (git doesn’t treat any branches differently from other branches), but it’s how git is traditionally used in a project.
If you are curious about the decision to use different default branch names, GitHub has an explanation of their change here: https://github.com/github/renaming
Now, if you switch back to the primary branch and make some more commits, your new branch won’t see any of those changes until you merge those changes onto your new branch.
Step 6: Create a new repository on GitHub
If you only want to keep track of your code locally, you don’t need to use GitHub. But if you want to work with a team, you can use GitHub to collaboratively modify the project’s code.
To create a new repo on GitHub, log in and go to the GitHub home page. You can find the “New repository” option under the “+” sign next to your profile picture, in the top right corner of the navbar:
After clicking the button, GitHub will ask you to name your repo and provide a brief description:
When you’re done filling out the information, press the ‘Create repository’ button to make your new repo.
GitHub will ask if you want to create a new repo from scratch or if you want to add a repo you have created locally. In this case, since we’ve already created a new repo locally, we want to push that onto GitHub so follow the ‘….or push an existing repository from the command line’ section:
myname:myproject myname$ git remote add origin https://github.com/desirit/newrepo.git
git branch -M main
git push -u origin main
Enumerating objects: 3, done.
Counting objects: 100% (3/3), done.
Writing objects: 100% (3/3), 235 bytes | 235.00 KiB/s, done.
Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/desirit/newrepo.git
* [new branch] main -> main
branch 'main' set up to track 'origin/main'.
(You’ll want to change the URL in the first command line to what GitHub lists in this section since your GitHub username and repo name are different.)
Step 7: Push a branch to GitHub
Now we’ll push the commit in your branch to your new GitHub repo. This allows other people to see the changes you’ve made. If they’re approved by the repository’s owner, the changes can then be merged into the primary branch.
To push changes onto a new branch on GitHub, you’ll want to run git push origin yourbranchname. GitHub will automatically create the branch for you on the remote repository:
myname:myproject myname$ git push origin my-new-branch
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 313 bytes | 0 bytes/s, done.
Total 3 (delta 0), reused 0 (delta 0)
To https://github.com/cubeton/mynewrepository.git
* [new branch] my-new-branch -> my-new-branch
You might be wondering what that “origin” word means in the command above. What happens is that when you clone a remote repository to your local machine, git creates an alias for you. In nearly all cases this alias is called “origin." It’s essentially shorthand for the remote repository’s URL. So, to push your changes to the remote repository, you could’ve used either the command: git push git@github.com:git/git.git yourbranchname or git push origin yourbranchname
(If this is your first time using GitHub locally, it might prompt you to log in with your GitHub username and password.)
If you refresh the GitHub page, you’ll see note saying a branch with your name has just been pushed into the repository. You can also click the ‘branches’ link to see your branch listed there.
Now click the green button in the screenshot above. We’re going to make a pull request!
Step 8: Create a pull request (PR)
A pull request (or PR) is a way to alert a repo’s owners that you want to make some changes to their code. It allows them to review the code and make sure it looks good before putting your changes on the primary branch.
This is what the PR page looks like before you’ve submitted it:
And this is what it looks like once you’ve submitted the PR request:
You might see a big green button at the bottom that says ‘Merge pull request’. Clicking this means you’ll merge your changes into the primary branch..
Sometimes you’ll be a co-owner or the sole owner of a repo, in which case you may not need to create a PR to merge your changes. However, it’s still a good idea to make one so you can keep a more complete history of your updates and to make sure you always create a new branch when making changes.
Step 9: Merge a PR
Go ahead and click the green ‘Merge pull request’ button. This will merge your changes into the primary branch.
When you’re done, I recommend deleting your branch (too many branches can become messy), so hit that grey ‘Delete branch’ button as well.
You can double check that your commits were merged by clicking on the ‘Commits’ link on the first page of your new repo.
Step 10: Get changes on GitHub back to your computer
Right now, the repo on GitHub looks a little different than what you have on your local machine. For example, the commit you made in your branch and merged into the primary branch doesn’t exist in the primary branch on your local machine.
In order to get the most recent changes that you or others have merged on GitHub, use the git pull origin master command (when working on the primary branch). In most cases, this can be shortened to “git pull”.
myname:myproject myname$ git pull origin main
remote: Enumerating objects: 8, done.
remote: Counting objects: 100% (8/8), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 7 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (7/7), 1.91 KiB | 325.00 KiB/s, done.
From https://github.com/desirit/newrepo
* branch main -> FETCH_HEAD
33b44a1..2dd540e main -> origin/main
Updating 33b44a1..2dd540e
Fast-forward
readme.md | 2 ++
1 file changed, 2 insertions(+)
create mode 100644 readme.md
This shows you all the files that have changed and how they’ve changed.
Now we can use the git log command again to see all new commits.
(You may need to switch branches back to the primary branch. You can do that using the git checkout master command.)
myname:myproject myname$ git log
commit 2dd540ef82f60ce22c24f82904ca916d44ac5571 (HEAD -> main, origin/main)
Merge: 764b394 71612fb
Author: desirit <5672758+desirit@users.noreply.github.com>
Date: Tue Nov 1 23:42:12 2022 -0400
Merge pull request #1 from desirit/desirit-patch-1
Update readme.md
commit 71612fbae79fd053a1007f9c6c6f5f1601ad59cc
Author: desirit <5672758+desirit@users.noreply.github.com>
Date: Tue Nov 1 23:40:52 2022 -0400
Update readme.md
commit 764b3940f7711f0d01aa1405e52b0add89b492f5
Author: desirit <5672758+desirit@users.noreply.github.com>
Date: Tue Nov 1 23:39:38 2022 -0400
Create readme.md
commit 33b44a1208e07be420ed8abe683f769d1029010a
Author: desirit <5672758+desirit@users.noreply.github.com>
Date: Tue Nov 1 23:32:15 2022 -0400
Your message about the commit
Step 11: Congratulations !!
You’ve successfully made a PR and merged your code to the primary branch. Congratulations! If you’d like to dive deeper, check out these more advanced tutorials and resources:
- https://training.github.com/ Github’s official git cheat sheets! Handy for remembering the everyday commands you’ll use.
- https://learngitbranching.js.org/ Confused or intrigued by git’s branch system? That just means you’re human! It’s one of the deepest parts of git, but also arguably the most powerful. Understanding the branch model gives you git superpowers, and this tutorial gives you a way to learn git branches in a visual, intuitive way.
- https://git-school.github.io/visualizing-git Another tool for exploring git visually. This one is more of an open-ended sandbox than learngitbranching.js.org
- https://github.com/jlord/git-it-electron A desktop application that helps you learn git through challenges you have to solve. It has a series of levels, each requiring you to use git commands to arrive at a correct answer.
- https://github.com/Gazler/githug If you liked git-it, Githug is another puzzle-based tutorial designed to give you a practical way of learning git.
Of course, that’s only scratching the surface, because when it comes to the question “What is GitHub?” the answer is all about what it can do for you.