Reputation: 3928

commits not showing up on github

I created a new repository on github.
I selected one of the options that added a README.md.
I then cd into the project on my hard drive.
I ran git init: Initialized empty Git repository in /Users/myusername/github/myproject/.git/

I ran "git add ." and then "git commit -m 'project files'", which responded with this:

[master (root-commit) ca52fe0] project files
 981 files changed, 257939 insertions(+), 0 deletions(-)
 create mode 100644 index.php
 create mode 100644 license.txt
 create mode 100644 readme.html
 create mode 100644 wp-activate.php
 ...

I then ran "git remote add origin https://github.com/myusername/myproject.git"
I then ran "git push origin master"
I then ran "git status" which said nothing to commit

But I look at repo and my "my project files" commit is not there. So then I ran git pull and got this:

You asked me to pull without telling me which branch you
want to merge with, and 'branch.master.merge' in
your configuration file does not tell me, either. Please
specify which branch you want to use on the command line and
try again (e.g. 'git pull <repository> <refspec>').
See git-pull(1) for details.

and then git push and checked again and still my commits are not on github repo. The only time I can see the commit is when I run "git log":

MacBook-myproject myusername$ git log
commit ca52fe090e6dbf1b6aa6ee51c3283efbe7549904
Author: User <myemailaddress>
Date:   Sat Jun 23 19:22:05 2012 -0400
project files

I followed github directions best that I could. What am I doing wrong?

Upvotes: 31

Answers (4)

Asad Khan

Reputation: 1

I think most times it happens with new users who are not familiar with branches. branches . check the branches if you have more than one. I think you are pushing changes to another branch.

Upvotes: 0

Christopher Peisert

Reputation: 24194

After your Github repository has been created (i.e. you can view it on Github), then you should already have:

1. Local repository set up:

git init

2. README file created and added to the repository:

touch README.md
git add README.md 
git commit -m 'first commit'

3. A remote called `origin` linked to your repository:

git remote add origin https://github.com/username/repo.git

4. An initial push, which copied your local README to your Github repository:

git push -u origin master

If you can view your repository on Github, then it has been successfully created. In this case it looks like you may have edited your README file on Github using the online editing tools, which caused your remote and local branches to diverge.

Before you can push your local changes to Github, you need to fetch or pull your remote changes, merge the changes locally (merging is automatic with pull), and then push to the remote.

See Pro Git: Fetching and Pulling from Your Remotes

Upvotes: 29

Hitesh Sahu

Reputation: 45150

After a git commit you need to push the changes

git push origin master to push in master branch

git push origin branch_name to push in secondary branch

Complete work flow for a branch:

git checkout -b aosp_in_docker //checkout a branch and switch into it
git branch // to check all branches current branch will have * sign
git status //to check status of file
git add .  //add untraced files
git commit -a -m 'added a docker container'
git push origin aosp_in_docker // push changes
git staus // check if success

Upvotes: 4

Zachariah Moreno

Reputation: 125

When you created the repository on GitHub you selected initializes remotely containing a README.md file. The next step would be to run git clone https://github.com/username/repo.git in your terminal. At this point you have a local copy on the GitHub repository, so you would then move in your project files. Run git add * then git commit -m 'first commit' then git push origin master. Your changes should now be visible on GitHub.