1. 3
    Add a Project and Push Changes to GitHub with git
    6m 1s

Add a Project and Push Changes to GitHub with git

Andy Van Slaars
InstructorAndy Van Slaars
Share this video with your friends

Social Share Links

Send Tweet
Published 6 years ago
Updated 5 years ago

In this lesson, we’ll create a new repository on GitHub, set the remote on our local repository and push our changes up to GitHub. We’ll add a readme, look at how our git status changes when we have changes that aren’t yet on the remote and we’ll see how running npm init again will update our package.json with new information.

Instructor: [00:00] Right now, this project is configured as a Git repository locally. I'd like to also be able to push it up to GitHub. I'm going to go to github.com and log in.

[00:11] Once logged in, I'm going to use this plus sign in the top-right corner to choose New repository. It's going to bring me to a form where I can choose my owner and give it a repository name. In my case, I'm going to call it egghead-react-boilerplate. Then I'm going to give it a description.

[00:39] This is going to be the output for this Modern Tooling with JavaScript course. I'm going to make it public. I'm going to leave all this as the defaults. I'm going to click the green Create repository button at the bottom. Then I'm going to get this page. I'm going to get some setup instructions, depending on my scenario.

[00:58] Since we've already created a local repository, we're going to scroll down to the Push an existing repository from the command line option. I could use this clipboard icon over here to copy both of these commands, but we're going to take these one step at a time.

[01:11] Let's start by copying the first line, the git remote add origin and then our address. I'll copy that. Then I'm going to come back into the terminal. I'm going to start, and I'm going to type git remote -v. This is going to show us a list of our remote repos, places that we can push this local repository to be online. We'll see that it returns no results.

[01:38] Let's paste that code that we copied from GitHub. I'll press Enter. Then I'm going to run git remote -v a second time. Now we'll see that we have two entries. We have one for fetch and one for push. Both are named origin. Both are using that GitHub address.

[01:56] With our remote in place, let's go back to the GitHub page. Let's take this second line. This is going to allow us to push our master branch up to that origin remote. I'll copy that. I'll come back here, paste. We'll see that it's pushed our branch from our local master to our remote master.

[02:18] Let's go back to GitHub, and let's refresh the page. Now we'll see that it has our name and description. It's showing our package.json and our initial commit.

[02:29] We'll see this little message here. It says, "Help people interested in this repository understand your project by adding a README." We have a green button where we can add it directly on GitHub, but instead let's go back to our project and add a README there.

[02:44] I'm going to reveal my files here. I'm going to add a new file. I'll call it README.md, because this is a Markdown file. Then we're going to add a title. We'll say react-boilerplate. We can add more details later. We'll save that.

[03:03] Then I'm going to go back into the terminal. I'm going to run git status. We'll see that we have an untracked file because we created this README, but we haven't added it to Git yet. We can do that by running a git add README.md.

[03:20] If we get status again, we'll see that we have a new change that's ready to be committed. It's staged, but it hasn't been committed yet. We'll commit with git commit -m. We'll give it a descriptive summary. We'll say, "Added a README." That's been added.

[03:45] We can get status again. We'll see that there's a message here. It says, "Your branch is ahead of 'origin/master' by 1 commit." We've made a local commit. We haven't pushed it up yet. We can push that by running git push. We'll see that it's pushed our master update to our remote master.

[04:08] If we go back to GitHub and we refresh the page, we'll see now there's a README in our file list. It's going to show us this README as the default contents of this repository's page on GitHub.

[04:20] Now we have GitHub set up as our remote for our repository. Let's go back to our code. In the terminal, I'm actually going to run a second npm init. I'm going to pass it the -y flag and let it do its default thing this time.

[04:37] We're going to see that we're going to get this preview. We'll see that our name is the same. The version is what we specified originally when we created this. Description, main scripts, all that has stayed the same, but now we have these repository bugs and home page fields.

[04:51] This has all been added because npm was able to see our local .git directory, which is hidden from view on our file list, and pull out our remote repository information. It's defaulted the bug URL to GitHub issues, the home page to the README. Our repository information knows it's a Git repository. It gives it the URL.

[05:15] With that done, if I run git status, we're going to see that we've modified our package.json. It needs to be committed. I'm going to add that to be committed. I'm going to do a commit with git commit -m. Then we'll say that I updated the package.json.

[05:38] If I run a status after that, we'll see that our local branch is ahead by 1 commit. We can push that up. If I check the status again, everything is good. If I refresh GitHub, we'll see that it has that latest updated package.json commit applied to it.

~ 36 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today