## TL;DR

Use

    git log &lt;branch&gt;

where `&lt;branch&gt;` is the name of the branch of interest.

## From the `git-log` man-page...

A simplified version of the `git-log` synopsis given in [that command&#39;s man page](http://git-scm.com/docs/git-log) is

    git log [&lt;revision range&gt;]

Further down, you can find the following passage:

&gt; When no `&lt;revision range&gt;` is specified, it defaults to `HEAD` (i.e. the whole history leading to the current commit)

In others words, `git log` is equivalent to `git log HEAD`. If you&#39;re on a branch, called `mybranch`, say, this command is also equivalent to `git log mybranch`.

You want to limit the log to commits reachable from another branch, i.e. a branch you&#39;re not currently on. The easiest way to do that is to explicitly pass the name of the branch of interest to `git log`:

    git log &lt;branchname&gt;

See the [gitrevisions manpage](http://git-scm.com/docs/gitrevisions) for more details about the many forms that the `&lt;revision-range&gt;` argument can take.

I read through the [TypeScript Coding guidelines][1]

And I found this statement rather puzzling:
&gt; Do not use &quot;I&quot; as a prefix for interface names

I mean something like this wouldn&#39;t make a lot of sense without the &quot;I&quot; prefix

    class Engine implements IEngine

Am I missing something obvious?

Another thing I didn&#39;t quite understand was this:

&gt; **Classes**
&gt; 
&gt; For consistency, do not use classes in the core compiler pipeline. Use
&gt; function closures instead.

Does that state that I shouldn&#39;t use classes at all?

Hope someone can clear it up for me :)

  [1]: https://github.com/Microsoft/TypeScript/wiki/Coding-guidelines

Confused about the Interface and Class coding guidelines for TypeScript

I want to show android `Snackbar` `(android.support.design.widget.Snackbar)` when the activity starts just like we show a `Toast`. 

But the problem is we have to specify the parent layout when creating `Snackbar` like this:

    Snackbar.make(parentlayout, &quot;This is main activity&quot;, Snackbar.LENGTH_LONG)
                .setAction(&quot;CLOSE&quot;, new View.OnClickListener() {
                    @Override
                    public void onClick(View view) {

                    }
                })
                .setActionTextColor(getResources().getColor(android.R.color.holo_red_light ))
                .show();

How to give parent layout when we show `Snackbar` at the start of the activity without any click events (If it was a click event we could&#39;ve easily pass the parent view)?

How to show Snackbar when Activity starts?

I&#39;m on a branch with some changes.  Changing branch is a pain as some files are locked by processes, so to change branch I&#39;d have to stop all the processes which have locks, then `stash` the changes before checking out the other branch to see its log.

Is it possible to view the log for a different branch, without having to check it out?

How can I print the log for a branch other than the current one?

<p>I'm on a branch with some changes.  Changing branch is a pain as some files are locked by processes, so to change branch I'd have to stop all the processes which have locks, then <code>stash</code> the changes before checking out the other branch to see its log.</p>
<p>Is it possible to view the log for a different branch, without having to check it out?</p>


I have read relevant questions about git merge and git rebase on SO, but I still cannot fully understand what is happening under the hood.

Here is our branching situation:

    MASTER------------------------
            \        \
             \        \----Feature B---
              \                        \
               \-----Feature A----------\---Feature A+B

Given 2 feature branches that stem from master at different times, we now want to combine the 2 branches. We want to follow the `first rebase then merge` practice, but when we rebase Feature A onto Feature B, we get conflicts. That&#39;s expected, because both features (and master) have changes in the same areas. But the strange thing is that the same conflict keeps reappearing after `git rebase --continue`. This drives us crazy, so we end up aborting the rebase, and use `git merge`. It turns out the conflicts are actually easy to resolve.

My question is two-fold:

 1. Is `git rebase` suitable for our situation? Or is rebase only good for pulling in a few (e.g., 1 or 2) changes?
 2. What is happening under the hood that causes the same conflict to reappear again and again? My understanding is `rebase` resolves conflicts one at a time, but which commit does it compare, and what does it compare it to?

Relavant posts on SO:

 - https://stackoverflow.com/questions/13825079/git-rebase-why-i-have-to-resolve-the-same-conflict-over-and-over
 - https://stackoverflow.com/questions/7241678/how-to-prevent-lot-of-git-conflicts-when-git-rebasing-lot-of-commits\
 - https://stackoverflow.com/questions/3516899/git-rebase-resolve-conflicts-again-and-again


Why does the same conflict reappear when I use git rebase?

I need some help. It is possible to only show one commit id? Since git log -3 show the log from 1 - 3, I just want to show only 3. What possible command will match for it?

I use the command

           git log -3 --pretty=format:&quot;%h&quot;

the result is
 
           ffbef87
           cf0e073
           1c76c5d

I only want to display the **1c76c5d** only.

            

git log show one commit id only

I want to do a `git pull` but only till a specific commit.

     A-&gt;B-&gt;C-&gt;D-&gt;E-&gt;F (Remote master HEAD)

so suppose my `local master` HEAD points to `B`, and I want to pull till `E`. What should I do ?

This is not pulling a specific commit, this is pulling upto a specific commit.

Git pull till a particular commit

I&#39;m using **GIT** and am trying to push my code and getting the following error when using the ***Terminal***. I don&#39;t use **XCode**, I&#39;m using ***Android Studio***.

The command I tried using was: 

&gt; git branch Networking

Error:

&gt; xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun`

I am running on **El Capitan Beta 4** update if that helps in any way.

---

&gt; **Update**: This also happens for **IntelliJ** users, and for **MacOS
&gt; Catalina** update

change xcrun developer path for Android Studio/IntelliJ

I would like to publish a npm package that contains my source as well as distribution files. My Github repository contains `src` folder which contains JavaScript source files. The build process generates `dist` folder that contains the distribution files. Of course, the `dist` folder is not checked into the Github repository.

How do I publish a npm package in a way that when someone does `npm install`, they get `src` as well as `dist` folder? Currently when I run `npm publish` from my git repository, it results in only `src` folder being published.

My package.json looks like this:

    {
      &quot;name&quot;: &quot;join-js&quot;,
      &quot;version&quot;: &quot;0.0.1&quot;,
      &quot;homepage&quot;: &quot;https://github.com/archfirst/joinjs&quot;,
      &quot;repository&quot;: {
        &quot;type&quot;: &quot;git&quot;,
        &quot;url&quot;: &quot;https://github.com/archfirst/joinjs.git&quot;
      },
      &quot;main&quot;: &quot;dist/index.js&quot;,
      &quot;scripts&quot;: {
        &quot;test&quot;: &quot;gulp&quot;,
        &quot;build&quot;: &quot;gulp build&quot;,
        &quot;prepublish&quot;: &quot;npm run build&quot;
      },
      &quot;dependencies&quot;: {
        ...
      },
      &quot;devDependencies&quot;: {
        ...
      }
    }


How to publish an npm package with distribution files?

So my history looks like this:

```
o---o---o---o  master
     \
      o---o---o  A
               \
                o B
```

So, to explain:

- I have branch `A` which was started from `master`
- I have branch `B` (with only 1 commit) which was started from `A`

What I want is this:

```
o---o---o---o  master
             \
              o---o---o  A
                       \
                        o B
```

---

What I did was:

1).

```
git checkout A
git rebase master
```

This resulted in a lot of conflicts which, after some significant time spent fixing, the following history emerged:

```
o---o---o---o  master
             \
              o---o---o  A
```

Which is exactly what I wanted.

(I don&#39;t know where `B` is right now)

---

2).

After this I did a lot of squashes and changed the order of commits on `A`, to make the history look like I want.

---

3).

Now, what I also want to do is:

```
git checkout B
git rebase A
```

However this doesn&#39;t seem to work and I don&#39;t know why. If I do `git log` I see the commits which were there before I did step 1.

Also, I get the same huge number of conflicts which I already solved at step 1. I spent significant time doing it, don&#39;t want to do it again.

[This example](https://stackoverflow.com/questions/27445747/how-to-rebase-over-already-rebased-branch) suggested to use `--onto`, which I did:

```
git checkout B
git rebase --onto A
```

But this deletes the commit on `B` entirely and makes `A` and `B` point to the same commit i.e. the last one on `A`.

---

My question is: **How can I effectively rebase B off A so that it looks like B started from A** ? (which was actually true in the beginning).

My best guess is that I&#39;m using `--onto` wrong. Or that I should use something else (like `cherry-pick`).

How to rebase a branch off a rebased branch?

I know similar questions have already been asked.

But, I believe my issue is due to a mistake I have previously made and therefore is different: let me explain.

Everything was working smoothly, as I could:

 - `git add .` all the files from my local repository.
 - `git commit -m &quot;message here&quot;` to add messages to my commits.
 - `git push origin master` to upload my files to GitHub.
 - `git push heroku master` to upload my files to Heroku.

However, at some point, I created a new branch locally called `add-calendar-model` in case next steps of the app development would go south...

... which is exactly what happened.

However, despite many attempts, I did not manage to get the initial code — i.e. the code from before I created the new branch — from the `master` branch to my local repository.

So, I decided to manually delete all the files from my local repository and `git clone` my `master` branch from GitHub.

This way, I got all my files back, but now, I cannot push any more to the remote repository.

Any time I try to run `git push origin add-calendar-model` or `git push origin master`, I get the following error:

    fatal: &#39;origin&#39; does not appear to be a git repository
    fatal: Could not read from remote repository.
    
    Please make sure you have the correct access rights
    and the repository exists.

I am not very comfortable with Git and GitHub, as you may have guessed by now, and I have to admit that I have no clue about how to fix this.

Any idea?

Git push: &quot;fatal &#39;origin&#39; does not appear to be a git repository - fatal Could not read from remote repository.&quot;

I have a problem when I push my codes to git while I have developer access in my project, but everything is okay when I have master access. Where is the problem come from? And how to fix it?

Error message: 

&gt; error: You are not allowed to push code to protected branches on this project.  
&gt; ...  
&gt; error: failed to push some refs to ...

Fix GitLab error: &quot;you are not allowed to push code to protected branches on this project&quot;?

I&#39;m aware that branches don&#39;t really store creator information - and they&#39;re just a pointer to a commit. 

My goal is to be able to clean out my old branches that have been merged back to the main branch, and list branches where this hasn&#39;t been done either. (A clean up). 

This is different to &quot;finding unmerged branches&quot; because I want to find merged branches as well, and I want to do it by author. 

My question is: **Is there a script to list git branches created by me?**

Is there a script to list git branches created by me?

Using `git branch --all` shows all *remote* and *local* branches. When does Git refresh this list?

On pull/push? And how do I refresh it using [Git Bash][1]?

  [1]: https://superuser.com/questions/1053633


When does Git refresh the list of remote branches?

In Git, I was trying to do a `squash commit` by merging in another branch and then resetting `HEAD` to the previous place via:

    git reset origin/master

But I need to step out of this. How can I move HEAD back to the previous location?

I have the SHA-1 fragment (`23b6772`) of the commit that I need to move it to. How can I get back to this commit?


How can I move HEAD back to a previous location? (Detached head) &amp; Undo commits

when I checkout remote git tag use command like this:

    git checkout -b local_branch_name origin/remote_tag_name

I got error like this:
    
&gt; error: pathspec `origin/remote_tag_name` did not match any file(s) known to git.

I can find remote_tag_name when I use git tag command.

What is git tag, How to create tags &amp; How to checkout git remote tag(s)

I am having difficulty in doing a pull from `origin`. I keep getting:

&gt; &quot;Cannot pull because there are uncommitted changes. Commit or undo your changes before pulling again. See the Output window for details.&quot;

This also applies to switching branches. I get a similar sort of message, but this does not always happen.

I am using Visual Studio 2015 Update 1 and Visual Studio Team Services Git. On my machine I have a local `master` branch, and development branches. Every time I switch to `master` and then I do a pull I get the error message. I have resorted to doing a stash and drop stash (command line) and sometimes I use [TortoiseGit][1] to do the pull and it works.

What is strange is even if I try to revert (on the uncommitted files) using TortoiseGit it shows that it was reverted successfully (I have already tried Visual Studio undo, nothing happens). Trying to pull again, it is still the same problem. The uncommitted files will be there and sometimes when I do a `git status` it says there is nothing to commit.

Just a note: This can happen even after switching from a branch onto `master`. In this case there is no way there can be uncommitted changes, because I would not have been able to switch in the first place.

I am still new to Git, but I would like to know if there is a better way of solving this as I would like to use one environment instead of using switching between different environments for each task; it&#39;s easier for me to just do everything from Visual Studio. I have already read up on:

*https://stackoverflow.com/questions/26885057/tfs-git-in-vs-cannot-switch-to-master-because-there-are-uncommitted-changes*

**UPDATE**

It seems like this problem has to do with line endings.

By doing a `git diff -R` you can see that a line ending has been added, &quot;^M&quot;, and it is different. Removing the `* text=auto` in gitattributes (then check for changes) and putting it back on again so that the gitattributes does not signal a change of itself that needs to be committed seems to help, there will not be any changes.

  [1]: http://en.wikipedia.org/wiki/TortoiseGit


Visual Studio 2015 Git error message &quot;Cannot pull/switch because there are uncommitted changes&quot;

I&#39;ve been doing my project while at some point I discovered that one thing stopped working. I needed to look up the state of my code when it was working correctly, so I&#39;ve decided to use git checkout (because I wanted to check-something-out). And so I&#39;ve done

    git checkout SHA

couple times while going back to point from which I can&#39;t go to HEAD, the output is following:

    git checkout SHA-HEAD
    
    error: Your local changes to the following files would be overwritten by checkout:
    	[list of files]
    Please, commit your changes or stash them before you can switch branches.
    Aborting

I am pretty much sure I have NOT changed anything. The command

    git checkout master

gives the same output.

Is there a way to go back to HEAD?

What is the safe way of &quot;jumping over&quot; history commits?


Git checkout - switching back to HEAD

This command fetches **all** tags:

    git fetch origin --tags

This command fetches a specific tag:

    git fetch origin refs/tags/1.0.0

**But** that doesn&#39;t let me do:

    git checkout tags/2.3.18

How can I fetch a single tag and then perform a checkout?

Fetch a single tag from remote repository

Here is my case:

 - I was working on one branch.
 - Pushed new commits to the remote.
 - Switched back to the master branch. 

But suddenly after typing `git checkout master` command my computer encountered [blue screen of death][1] and an unexpected force shut down happened. After starting back my computer I have checked the status of my current branch and as a result I got each and every file as marked new files.

Now, I am stuck at this point and after `git log` command I am getting error 

    $ git log
    fatal: your current branch appears to be broken

How to solve this problem and recover my branch?.

I am working with windows 7 and git bash latest version

&gt; Edit: **I don&#39;t want to delete this branch.**


  [1]: https://en.wikipedia.org/wiki/Blue_Screen_of_Death

Broken branch in git, fatal: your current branch appears to be broken

I&#39;m trying to view commits made by a specific user, and want to remove any  merges done by the user from the output. How can I do so?

I can check for the commits of a user using `git log --author=&lt;name&gt;`, but can&#39;t remove the merge commits in the output.

PS: Merge conflicts do not happen in the workflow of the repo in question, all branches are rebased before merging into master so it is safe to remove the merge commits from the output, and similarly, two feature branches are not merged with one another raising the possiblity.

View git log without merge commits

IntelliJ supports git stashes as well as it&#39;s own built in shelve command. These seem to be almost identical in purpose and utility. What is the difference between them?

What is the difference between IntelliJ&#39;s Shelve and Git stash?

On my windows machine `git stash` has about 3.5 seconds overhead on each invocation, which adds about 7 seconds to my git commit hook.

The same command under linux (same machine) takes about 0.01 seconds. The performance issue applies to empty repositories as well.

I have tried the following from [this thread](https://stackoverflow.com/questions/4485059/git-bash-is-extremely-slow-in-windows-7-x64) and [this thread](https://stackoverflow.com/questions/2835775/msysgit-bash-is-horrendously-slow-in-windows-7/2967519#2967519):

- `core.fscache` is set to `true`
- `core.preloadindex` is set to `true`
- `gc.auto` is set to `256`
- Setting PS1=&#39;$ &#39;
- Running cmd in administration mode
- Running inside *cmd.exe* instead of git-bash

Running `GIT_TRACE=true git stash list`


    16:58:16.844591 git.c:563               trace: exec: &#39;git-stash&#39; &#39;list&#39;
    16:58:16.844591 run-command.c:336       trace: run_command: &#39;git-stash&#39; &#39;list&#39;
    16:58:19.699591 git.c:350               trace: built-in: git &#39;rev-parse&#39; &#39;--git-dir&#39;
    16:58:19.859591 git.c:350               trace: built-in: git &#39;rev-parse&#39; &#39;--git-path&#39; &#39;objects&#39;
    16:58:20.069591 git.c:350               trace: built-in: git &#39;rev-parse&#39; &#39;--show-toplevel&#39;
    16:58:20.154591 git.c:350               trace: built-in: git &#39;rev-parse&#39; &#39;--git-path&#39; &#39;index&#39;
    16:58:20.244591 git.c:350               trace: built-in: git &#39;config&#39; &#39;--get-colorbool&#39; &#39;color.interactive&#39;
    16:58:20.334591 git.c:350               trace: built-in: git &#39;config&#39; &#39;--get-color&#39; &#39;color.interactive.help&#39; &#39;red bold&#39;
    16:58:20.424591 git.c:350               trace: built-in: git &#39;config&#39; &#39;--get-color&#39; &#39;&#39; &#39;reset&#39;
    16:58:20.514591 git.c:350               trace: built-in: git &#39;rev-parse&#39; &#39;--verify&#39; &#39;--quiet&#39; &#39;refs/stash&#39;
    
    real    0m3.845s
    user    0m0.000s
    sys     0m0.047s


Running `GIT_TRACE_PERFORMANCE=true git stash list`


    16:59:18.414591 trace.c:420             performance: 0.001078046 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;rev-parse&#39; &#39;--git-dir&#39;                                          
    16:59:18.569591 trace.c:420             performance: 0.000947184 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;rev-parse&#39; &#39;--git-path&#39; &#39;objects&#39;                               
    16:59:18.779591 trace.c:420             performance: 0.001253627 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;rev-parse&#39; &#39;--show-toplevel&#39;                                    
    16:59:18.869591 trace.c:420             performance: 0.001285517 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;rev-parse&#39; &#39;--git-path&#39; &#39;index&#39;                                 
    16:59:18.955591 trace.c:420             performance: 0.001139994 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;config&#39; &#39;--get-colorbool&#39; &#39;color.interactive&#39;                   
    16:59:19.040591 trace.c:420             performance: 0.001182881 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;config&#39; &#39;--get-color&#39; &#39;color.interactive.help&#39; &#39;red bold&#39;       
    16:59:19.125591 trace.c:420             performance: 0.001128997 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;config&#39; &#39;--get-color&#39; &#39;&#39; &#39;reset&#39;                                
    16:59:19.215591 trace.c:420             performance: 0.001567766 s: git command: &#39;C:\Program Files\Git\mingw64\libexec\git-core\git.exe&#39; &#39;rev-parse&#39; &#39;--verify&#39; &#39;--quiet&#39; &#39;refs/stash&#39;                    
    16:59:19.295591 trace.c:420             performance: 3.730583540 s: git command: &#39;C:\Program Files\Git\mingw64\bin\git.exe&#39; &#39;stash&#39; &#39;list&#39;                                                                
                                                                                                                                                                                                              
    real    0m3.819s                                                                                                                                                                                          
    user    0m0.000s                                                                                                                                                                                          
    sys     0m0.062s                                                                                                                                                                                          


From the log we see that it takes around 3 seconds between the git-stash command is run and the git-rev-parse is run. Are there any other flags I can run to find the bottleneck?

git stash is slow on windows

When should I use `git stash save` instead of `git stash push` and vice-versa?

What&#39;s the difference between git stash save and git stash push?

I had a bunch of staged and unstaged changes and I wanted to quickly switch to another branch and then switch back.

So I staged my changes using:

    $ git stash push -a

(In hindsight I probably could have used `--include-untracked` instead of `--all`)

Then when I went to pop the stash I get a whole lot of errors along the lines of:

    $ git stash pop
    foo.txt already exists, no checkout
    bar.txt already exists, no checkout
    ...
    Could not restore untracked files from stash entry

There doesn&#39;t seem to be any changes restored from the stash.

I also tried `$ git stash branch temp` but that shows the same errors.

I did figure out a way around this which was to use:

    $ git stash show -p | git apply

Disaster averted for now but this raises some questions.

Why did this error happen in the first place and how do I avoid it next time?

Content Type	Original Author	Original Content on Stackoverflow
Question	BanksySan	View Question on Stackoverflow
Solution 1 - Git	jub0bs	View Answer on Stackoverflow

How can I print the log for a branch other than the current one?

Git Problem Overview

Git Solutions

Solution 1 - Git

TL;DR

From the `git-log` man-page...

How to show Snackbar when Activity starts?

Confused about the Interface and Class coding guidelines for TypeScript

Attributions

Git Problem Overview

Git Solutions

Solution 1 - Git

TL;DR

From the git-log man-page...

How to show Snackbar when Activity starts?

Confused about the Interface and Class coding guidelines for TypeScript

Attributions

From the `git-log` man-page...