The core use for `git checkout --orphan` is to create a branch in a `git init`-like state on a non-new repository.

Without this ability, *all* of your git branches would have a common ancestor, your initial commit.  This is a common case, but in no way the only one.  For example, git allows you to track multiple independent projects as different branches in a single repository.

That&#39;s why your files are being reported as “changes to be committed”: in a `git init` state, the first commit isn&#39;t created yet, so all files are new to git.

It&#39;s used by e.g. [GitHub Pages][1], which stores a repo&#39;s website inside the repo but on a separate branch. There&#39;s no reason to store anything but the website&#39;s history on this branch.


  [1]: http://pages.github.com/

We were moving to a public repo from a private one and because of sensitive commit information, we wanted to reset a branch  as `new` and push it as a blank branch. Here is a typical way of a workflow for that:

https://stackoverflow.com/questions/13716658/how-to-delete-all-commit-history-in-github

Another use case where this may be useful is build machines or virtual instances for testing that require specific .git folder settings (e.g. user, remote url) and all history discarded because of space limitations.
This is often the case with legacy setups that don&#39;t use containers such as Docker.

It would tipically be done for dedicated deployment branches instead of dealing with master. Once the new branch is pushed to remote, on the instance do:

    git clone [remote-url] --branch [name] --single-branch [folder]

Shallow clone would be a better option when working directly with master (not recommended):

    git clone -–depth [depth] [remote-url]

This is a tricky one, I have the following output:

&gt; mysqldump: Got error: 1045: Access denied for user &#39;root&#39;@&#39;localhost&#39; (using password: YES) when trying to connect

When attempting to export my database with `mysqldump` on Windows XP. The username is root, the password is correct and contains only alphanumeric characters. I have tried different cases, with/without quotes, specifying using `-u` and `-p`, specifying using `--user=` and `--password=` and other methods of specifying user/passwords etc, specifying the host (it&#39;s all local) and even specifying the database using `--databases` instead of just blank.  The error is always the same when using a password and always the same except the &quot;NO&quot; message when without.  I have tried many fixes found through searches with no success.  One fix suggested inspecting mysql.conf, but the Windows build doesn&#39;t seem to have one.  The credentials (and indeed commandline parameters) work perfectly with mysql.exe - this problem only seems to be affecting mysqldump.exe.

mysqldump Error 1045 Access denied despite correct passwords etc

Why does `NaN === NaN` return `false`  in Javascript?

    &gt; undefined === undefined
    true
    &gt; NaN === NaN
    false
    &gt; a = NaN
    NaN
    &gt; a === a
    false

On the [documentation page](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN) I see this:

&gt;## Testing against NaN
&gt;
&gt;Equality operator (`==` and `===`) cannot be used to test a value against `NaN`. Use `isNaN` instead.

Is there any reference that answers to the question? It would be welcome.


Why is NaN === NaN false?

I&#39;ve just discovered `git checkout --orphan`, but I don&#39;t know how to use it. Its help page says it creates a **new unparented branch**. 

In the `master` branch, I&#39;ve tried `git checkout --orphan br`, only to see the files in the working directory change to &amp;ldquo;Changes to be committed&amp;rdquo;, and the `git log` saying `fatal: bad default revision &#39;HEAD&#39;`.

So what&#39;s the advantage of using  `git checkout --orphan`?

What is `git checkout --orphan` used for?

I've just discovered <code>git checkout --orphan</code>, but I don't know how to use it. Its help page says it creates a new unparented branch.
In the <code>master</code> branch, I've tried <code>git checkout --orphan br</code>, only to see the files in the working directory change to “Changes to be committed”, and the <code>git log</code> saying <code>fatal: bad default revision 'HEAD'</code>.
So what's the advantage of using <code>git checkout --orphan</code>?

I have looked through many web pages on the new Git integration in VS 2013 and they do not deal with adding an existing solution to Github.  In fact I can&#39;t find much on using GitHub instead of Visual Studio Online.

Can anyone tell me how I start from an existing solution and add it to Github using the tools in VS 2013.


How do I add an existing Solution to GitHub from Visual Studio 2013

I&#39;ve already looked at the relevant docs from [git-scm.com](http://git-scm.com/book/ch2-3.html) and [gitref.org](http://gitref.org/inspect/), but I can&#39;t seem to figure this out. 

Let&#39;s say I want to get all commits for Tuesday, November 12th, 2013. Using an existing repo as an example, I know for a fact that I have commits on that day, as well as commits the day before and the day after. 

### With `2013-11-11` and `2013-11-12`
All the following give me commits for both November 11th and 12th:

* `git log --after=&quot;2013-11-11&quot; --until=&quot;2013-11-12&quot;`
* `git log --since=&quot;2013-11-11&quot; --until=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-11&quot; --before=&quot;2013-11-12&quot;`
* `git log --since=&quot;2013-11-11&quot; --before=&quot;2013-11-12&quot;`


### With `2013-11-12` only
All the following give me no commits:

* `git log --since=&quot;2013-11-12&quot; --until=&quot;2013-11-12&quot; ` 
* `git log --since=&quot;2013-11-12&quot; --before=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-12&quot; --until=&quot;2013-11-12&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-12&quot;` 

### With `2013-11-12` and `2013-11-13`
As expected (from the results of `2013-11-11` and `2013-11-12` above), all of the following give me results from both November 12th and 13th:

* `git log --since=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot;`
* `git log --since=&quot;2013-11-12&quot; --until=&quot;2013-11-13&quot;`
* `git log --after=&quot;2013-11-12&quot; --before=&quot;2013-11-13&quot; `

...and so on and so forth. I feel like I&#39;ve tried every possible combination of `since`, `after`, `before`, and `until` but still can&#39;t find the answer, nor do I understand whether those options are inclusive or exclusive, since they seem to be inclusive if the two dates are different, but exclusive if they&#39;re on the same day. Did I miss something / what am I doing wrong?! 

How do I view all commits for a specific day?

I&#39;ve been stuck all day on this issue, looking for an answer here :( ... 

**Context**

I&#39;m working alone on a project and I used github until now to save my work other than on my computer. 
Unfortunately, I added a very large file to the local repository : 300mb (which exceed Github&#39;s limit).

**What I did**

I will try to make an history of what I made :

1. I (dumbly) added everything to the index :
        
        git add *
        
2. I committed changes : 
        
        git commit -m &quot;Blablabla&quot;

3. I tried to push to origin master

        git push origin master 
It took a while, so I just CTRL+C, and repeated step 2 and 3 four times, until I realised that a file was too large to be pushed to github. 

4. I made the terrible mistake to delete my large file (I don&#39;t remember if I did a git rm or a simple rm)

5. I followed the instructions on (https://help.github.com/articles/remove-sensitive-data)

6. When I try to git filter branch, I get the following error : &quot;Cannot rewrite branches: You have unstaged changes.&quot;


Thanks in advance !






How to remove a too large file in a commit when my branch is ahead of master by 5 commits

On Github, you can make pull requests to add functionality to a project. One&#39;s contributions have to be on a branch that, if the request is accepted, will be merged into the master branch (or an analogous one) of the project.

Now, I submitted a pull request on Github and my contributions are on a branch called `patch-1`. I can modify the name of the branch locally by

    git branch -m patch-1 newname

and in principle I can also rename it on my forked repo on Github by following the instruction found in [this answer][1]. This is done in practice by removing the old branch, `patch-1` in my case, and repush it with a different name `newname`.

Is it allowed to rename the branch `patch-1` on my forked repository on Github when it constitutes a pull request?
Or it causes problems on the pull request management?

Is there any way to rename a branch on a forked repository on Github when that branch is a pull request?

  [1]: https://stackoverflow.com/a/9525744/1611927

Renaming a branch while on pull request

When I do a git status, I see files like this:

    modified:  dir/A/file.txt
    modified:  dir/B/file.txt
    modified:  dir/C/file.txt
    modified:  dir/D/file.txt

What I want to do is to discard changes to all files EXCEPT for dir/C/file.txt

I want to do something like this:

    git checkout -- dir/!C/file.txt



Git: Checkout all files except one

I find myself doing this a lot when cherry-picking a commit from another branch.

    $ git log -1 another_branch
    commit &lt;commit_sha&gt;
    // copy &lt;commit_sha&gt;
    $ git cherry-pick &lt;commit_sha&gt;

Can I do all of this in one command, if so, what is it?

How to cherry-pick the last sha from another branch in Git with 1 command?

I&#39;m more of a novice when it comes to advanced operations in git. I maintain my [blog](http://jatinganhotra.com) using the blogging framework [Octopress](http://octopress.org/). Though Octopress is not under any development since 2011, it serves my purpose well and so I haven&#39;t thought of changing anything so far.

FYI, my blog is hosted on Github Pages.  

Today, while working on a new post, `git status` showed the following message:

    On branch source
    Your branch is based on &#39;origin/master&#39;, but the upstream is gone.
      (use &quot;git branch --unset-upstream&quot; to fixup)

The same message repeated for all the subsequent commands such as `git add .`, `git commit -m &#39;message&#39;` and `git push origin source`.  

 - What does the message mean?  
 - Is something broken?  
 - If yes, what?  
 - Do I need to fix it? 

If possible, please point me to a pdf/web article where I can read up on this and understand it for future.

More details:

    bash-3.2$ git branch -a
    * source
      remotes/octopress/2.1
      remotes/octopress/HEAD -&gt; octopress/master
      remotes/octopress/gh-pages
      remotes/octopress/linklog
      remotes/octopress/master
      remotes/octopress/refactor_with_tests
      remotes/octopress/rubygemcli
      remotes/octopress/site
      remotes/origin/source

Please let me know if more information is needed. Thanks.

Why call git branch --unset-upstream to fixup?

I&#39;ve pulled all remote branches via `git fetch --all`. I can see the branch I&#39;d like to merge via `git branch -a` as remotes/origin/branchname. Problem is it is not accessible. I can&#39;t merge or checkout.

Git: Merge a Remote branch locally

How do I shallow clone a git repository, so that my clone contains only 1 history item, and starts on a specific branch?

I know how to do a shallow clone:

    git clone --depth 1 https://path/to/myrepo.git

 but not start the clone on a specific branch.


How do I shallow clone a repo on a specific branch?

Alright, lets say one day we make happen to make a bunch of modifications and when we go to commit them we notice we were working on the wrong branch.

How can we force git to switch branches **without discarding local changes**.

I&#39;m probably going to go about this in a naive way while I wait a reply, but I would like to know if theres a correct procedure as I&#39;d be lying if I said this hasn&#39;t happened to me before...

 - Backup changed repo
 - `git reset --hard`
 - `git checkout right-branch`
 - Restore changes
 - `git commit -m &quot;changes&quot;`


git switch branch without discarding local changes

I want to provide a git tag to the TeamCity server to build it.
I pass the tag (i.e. `release_1.1`) as a parameter to the job. So inside the job the tag is available as `%tag%`,  but under the `Version Control Settings` I don&#39;t see any way to use this parameter so the server can checkout this tag.
Is there any way this parameter can be used in the settings to checkout the tag?

How can I build a git tag in TeamCity?

*This question is similar to [this one][1], but more specific.*

I have a project with two branches: `staging` and `beta`. 
I develop on `staging`, and use the `master` branch to fix bugs. So if I&#39;m working on staging and I see an error, I change to `master` branch:

    git checkout master

and do the stuff:

    git add fileToAdd
    git commit -m &quot;bug fixed&quot;

and then I merge with both branches:

    git checkout staging
    git merge master
    git checkout beta
    git merge beta

And doesn&#39;t matter if there are other files on the working tree.

But now, **when I try to change to the `master` branch, I&#39;m getting an error**:

    error: Your local changes to the following files would be overwritten by checkout:
	src/Pro/ConvocationBundle/Controller/DefaultController.php
    Please, commit your changes or stash them before you can switch branches.
    Aborting
 
I thought that I should remove the file from the staging area:

    git reset HEAD src/Pro/ConvocationBundle/Controller/DefaultController.php

But I&#39;m getting the same error. If I do `git status`, I get `No changes to commit`

    


  [1]: https://stackoverflow.com/questions/14318234/how-to-ignore-error-on-git-pull-about-my-local-changes-would-be-overwritten-by-m

error: Your local changes to the following files would be overwritten by checkout

I sometimes use the `checkout -b` option to create a new branch, check it out at the same time and set up tracking in one command.

In a new environment, I get this error:

    $ git checkout -b test --track origin/master
    fatal: Cannot update paths and switch to branch &#39;test&#39; at the same time.
    Did you intend to checkout &#39;origin/master&#39; which can not be resolved as commit?

Why does Git not like it? This used to work with the same repo.

&quot;Cannot update paths and switch to branch at the same time&quot;

I have in my git repo, a file named xyz. Coincidently, I also have a branch named xyz. Presently I am on master, but I want to checkout to branch xyz. The command to be used is simple

    $ git checkout xyz

But this would checkout the file `xyz` to the present HEAD. How would I change my branch to branch `xyz`?


Content Type	Original Author	Original Content on Stackoverflow
Question	jsvisa	View Question on Stackoverflow
Solution 1 - Git	JB.	View Answer on Stackoverflow
Solution 2 - Git	Fred Foo	View Answer on Stackoverflow
Solution 3 - Git	user1767754	View Answer on Stackoverflow
Solution 4 - Git	Atanas Sariyski	View Answer on Stackoverflow

What is `git checkout --orphan` used for?

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

Solution 4 - Git

Why is NaN === NaN false?

mysqldump Error 1045 Access denied despite correct passwords etc

Attributions