One classic root cause for this message is:

- when the repo has been initialized (`git init lis4368/assignments`), 
- but **no commit has ever been made**

Ie, if you don&#39;t have added and committed at least once, there won&#39;t be a local `master` branch to push to.

Try first to create a commit:

- either by adding (`git add .`) then `git commit -m &quot;first commit&quot;`  
(assuming you have the right files in place to add to the index)
- or by create a first empty commit: `git commit --allow-empty -m &quot;Initial empty commit&quot;`

And then try `git push -u origin master` again.

See &quot;[Why do I need to explicitly push a new branch?][1]&quot; for more.


  [1]: https://stackoverflow.com/a/17096880/6309

It doesn&#39;t recognize that you have a master branch, but I found a way to get around it. I found out that there&#39;s nothing special about a master branch, you can just create another branch and call it master branch and that&#39;s what I did.

To create a master branch:

    git checkout -b master

And you can work off of that.

Is there any difference in pushing the master branch of a local git repository to the master branch of a remote repository called origin with `git push origin master`
or with `git push origin`?

What is the difference between git push origin and git push origin master

I think I&#39;ve got some funny expectations...  I want to iterate the numbers from 1 to 10. As a while loop it goes like this:

    def countMe = 1
    while (countMe&lt;11) {
      println countMe
      countMe++
    }

I was expecting that the following would do this also:

    [1..10].each { println it }

But it actually prints the `IntRange`, not each `Integer` in the range.  What is the (syntactically) closest way to my `[x..y].each{}` fantasy to get each of a list of numbers?

calling .each{} on IntRange returns the range not each integer

I am trying to add a file to my repository on BitBucket and I am having trouble.

I am using GIT and this is what I type in 

   

    $ cd lis4368/assignments
    $ git remote
    $ git remote -v
    $ git remote rm origin

and then I type this in (this is what BitBucket tells me to enter)

    $ git remote add origin https://cpb09e@bitbucket.org/cpb09e/cpb09e.git
    $ git push -u origin master

And I keep getting this error message: 

    error: src refspec master does not match any.
    error: failed to push some refs to &#39;https://cpb09e@bitbucket.org/cpb09e/cpb09e.git&#39;

Can someone pleas help me out? I have tried everything from git commit to rm -rf * and I cannot get anything to work at all.

Git error: src refspec master does not match any error: failed to push some refs

I am trying to add a file to my repository on BitBucket and I am having trouble.
I am using GIT and this is what I type in
<pre><code class="hljs language-shell">$ cd lis4368/assignments
$ git remote
$ git remote -v
$ git remote rm origin
</code></pre>
and then I type this in (this is what BitBucket tells me to enter)
<pre><code class="hljs language-shell">$ git remote add origin https://cpb09e@bitbucket.org/cpb09e/cpb09e.git
$ git push -u origin master
</code></pre>
And I keep getting this error message:
<pre><code class="hljs language-vbnet">error: src refspec master does not match any.
error: failed to push some refs to 'https://cpb09e@bitbucket.org/cpb09e/cpb09e.git'
</code></pre>
Can someone pleas help me out? I have tried everything from git commit to rm -rf * and I cannot get anything to work at all.

Is there a way to show the git-diff filtered by a given pattern.

Something like 

    git grepdiff pattern

    changed file
    +++ some sentence with pattern
    changed file 2
    --- some other pattern

Unfortunately the simplest solution is not good enough

    git diff | grep pattern 
    
    +++ some sentence with pattern
    --- some other pattern
    # not an option as doesn&#39;t put the filename close to the match

I came with a workaround using awk

    git diff | awk &quot;/\+\+\+/{f = \$2}; /PATTERN/ {print f \$0} &quot;

But would love to find out that there is a command for this.

How to grep the git diff?

How can I make a new `commit` and create a new message if no changes are made to files?

Is this not possible since the commit&#39;s code (SHA ?) will be the same?

How to commit no change and new message?

I am new to Git and I am using EGit eclipse plugin to commit.

I modified few files and I stashed the changes, then I did `git pull` in command line which pulled up all the latest commits. Then I did `Apply stashed changes` from EGit. Now it applied my changes and the changes which pulled from last commit of stashed files went out. I am not sure why it didn&#39;t ask me about merge conflicts and overwrote my changes and lost previous commits changes. 

How to get those changes?

git stash and git pull

If one tries to run any of the git-bisect commands from anywhere other than the root directory of the repository, one is told:

&gt; You need to run this command from the toplevel of the working tree.

Why is that? I know of no other git command that has this requirement, and I see no obvious reason that bisect should be special. The man page makes no mention of this restriction, either.

It&#39;s really not a big deal. I&#39;m mostly just curious.

Why does git-bisect have to be run from the top level directory of the working tree?

I have one repository which I want to push into Bitbucket and GitHub.
It is vital for my repository to be hosted by both.

Is there a way to do this in Git?

How to use Bitbucket and GitHub at the same time for one project?

I know I can get the project through `git clone` command, but is there any way, how to download the project through the web interface from [BitBucket.org][1]?
In the best way, I am looking for a way to download a project source as ZIP compress file.


  [1]: https://bitbucket.org/

BitBucket - download source as ZIP

When using Bitbucket for source control, there&#39;s an &quot;Approve&quot; button that appears at the upper right of the commit page:

![Bitbucket Approve Button][1]

It appears to generate an activity message in the repositories overview page:

![enter image description here][2]

Is that all it does? What is the intended purpose of that button? Is it just a social feature?


  [1]: http://i.stack.imgur.com/xvrkK.jpg
  [2]: http://i.stack.imgur.com/ccRwI.jpg

What does Approve button do with changeset on bitbucket.org?

I want to host my source on bitbucket using git because I obviously get a free private repo and I want to host my app on heroku using the source code from bitbucket. 

Can i do it using the github client and heroku toolbelt. Will it work? Github is great but i dont want everyone seeing my code and I dont want to pay for a private repo because its a small project.

Deploying to Heroku using git on bitbucket

I am using SourceTree (with BitBucket) to manage my code.  I have forked a repo, and the parent repo has been updated.

How do I use SourceTree to merge the upstream code into my forked repo?

How do I update my forked repo using SourceTree?

Scenario:  

1. I make a new branch&lt;br&gt;
2. hack on it&lt;br&gt;
3. commit it&lt;br&gt;
4. push it&lt;br&gt;
5. hack on it some more&lt;br&gt;
6. commit again&lt;br&gt;
7. try to push again&lt;br&gt;

Git responds:

&gt; Updates were rejected because the tip of your current branch is behind
its remote counterpart. etc.

I&#39;m the only one hacking on this branch - no one else is touching it.  The remote branch is actually *behind* the local branch.  I shouldn&#39;t have to pull at all.

(And if I do pull, Git reports conflicts between the two, and forces me to merge the branch into itself)

Why is this (likely) happening?  And how can I diagnose/fix it?

To be clear, I&#39;m not branching anywhere, and *no one else* is working on it:

    Remote: Commit A -------- Commit B  
  
    Local:  Commit A -------- Commit B -------- Commit C  
  

C is a straight continuation of B, no branching involved.  But git thinks C is a branch of A:  
  
    Remote: Commit A -------- Commit B  
      
                      ------- Commit C  
                    /  
    Local:  Commit A -------- Commit B  
  
It&#39;s not; it&#39;s a straight continuation of B.

Git says local branch is behind remote branch, but it&#39;s not

I&#39;ve been using Git for a while now and have recently downloaded an update only to find this warning message come up when I try to `push`.

    warning: push.default is unset; its implicit value is changing in 
    Git 2.0 from &#39;matching&#39; to &#39;simple&#39;. To squelch this message 
    and maintain the current behavior after the default changes, use: 
    
      git config --global push.default matching

    To squelch this message and adopt the new behavior now, use: 

      git config --global push.default simple


I can obviously set it to one of the values mentioned, but what do they mean? What&#39;s the difference between `simple` and `matching`?

If I change it on one client will I need to do anything on other clients that I share repos with?

Warning: push.default is unset; its implicit value is changing in Git 2.0

I am new to Git and have a fairly large project that I want to push to a remote repo (Repo B) on Github. The original project was on Github as well but from a different repo (Repo A). I have to make some changes to files from Repo A before I can setup the project up on Repo B. I have setup the remotes, ssh keys etc. and I run into an issue when pushing the codebase to Repo B.


I get the following error all the time:

    $ git push &lt;remote_repo_name&gt; master
    Enter passphrase for key &#39;/c/ssh/.ssh/id_rsa&#39;:
    Counting objects: 146106, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (35519/35519), done.
    fatal: pack exceeds maximum allowed size00 GiB | 154 KiB/s
    fatal: sha1 file &#39;&lt;stdout&gt;&#39; write error: Invalid arguments
    error: failed to push some refs to &#39;git@github.com:&lt;repo&gt;.git

I changed the following settings in my local gitconfig

    git config pack.packSizeLimit 1g
    git config pack.windowMemory 1g

... and ran git gc (which I see reorganized the packs so that each pack stayed within the packsize of 1GB). This did not work and I get the error seen above.

I tried to lower the size of each pack as well ....

    git config pack.packSizeLimit 500m
    git config pack.windowMemory 500m

... and ran git gc (which I see reorganized the packs so that each pack stayed within the packsize of 500MB). This did not work either and I ran into the same error.

I am not sure of what Github&#39;s default packsize limits are (if any). The account is a micro account if that matters.

Github remote push pack size exceeded

I&#39;ve a repository `moodle` on my Github account which I `forked` from the official repository.

I then cloned it on my local machine. It worked fine. I created several branches (under the `master` branch). I made several commits and it worked fine. 

I don&#39;t know how I&#39;m getting the following error when I do : `git push origin master`


    fatal: &#39;origin&#39; does not appear to be a git repository
    fatal: The remote end hung up unexpectedly

How do I resolve the error without effecting my repository on Github?

I&#39;m using `Ubuntu 12.10`

The contents of my `.git/config` after doing `cat $(git rev-parse --show-toplevel)/.git/config` gives:

    [core]
    	repositoryformatversion = 0
    	filemode = true
    	bare = false
    	logallrefupdates = true
    [branch &quot;master&quot;]
    [branch &quot;MOODLE_23_STABLE&quot;]
    [branch &quot;MOODLE_24_STABLE&quot;]
    [remote &quot;upstream&quot;]
    	url = git://git.moodle.org/moodle.git
    	fetch = +refs/heads/*:refs/remotes/upstream/*


Content Type	Original Author	Original Content on Stackoverflow
Question	user1676428	View Question on Stackoverflow
Solution 1 - Git	VonC	View Answer on Stackoverflow
Solution 2 - Git	Brice Lin	View Answer on Stackoverflow

Git error: src refspec master does not match any error: failed to push some refs

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

calling .each{} on IntRange returns the range not each integer

What is the difference between git push origin and git push origin master

Attributions