threads / discuss / 27435

git branch

Subject: git branch

## tl;dr

4 messages between May 23, 2011 and May 23, 2011.

replies: 3people: 3as markdown or json

Gergely Buday· May 23, 2011, 11:36 UTC · lore

Hi there,

I created

git branch install_2.0

for my install script. Then pushed to

git push origin install_2.0

so that github stores by branch

after another commit I tried to push again but git told me that I'm not on that branch. Why git loses the state that I'm on a branch? What should I do to have my expected behaviour?

- Gergely

Marcus Karlsson· May 23, 2011, 11:46 UTC · re: Gergely Buday · lore

Re: git branch

On Mon, May 23, 2011 at 01:36:09PM +0200, Gergely Buday wrote:

Show 17 quoted lines

> Hi there,
> 
> I created
> 
> git branch install_2.0
> 
> for my install script. Then pushed to
> 
> git push origin install_2.0
> 
> so that github stores by branch
> 
> after another commit I tried to push again but git told me that I'm
> not on that branch. Why git loses the state that I'm on a branch? What
> should I do to have my expected behaviour?
> 
> - Gergely

I'm not sure if I'm following you correctly, but with Git you need to check out your branch after creating it. Run git checkout install_2.0 after you have created it.

	Marcus

Gergely Buday· May 23, 2011, 12:17 UTC · re: Marcus Karlsson · lore

Re: git branch

> I'm not sure if I'm following you correctly, but with Git you need to
> check out your branch after creating it. Run git checkout install_2.0
> after you have created it.

Yes, that sounds reasonable. I did not know it was necessary to "switch to it".

- Gergely

Tim Mazid· May 23, 2011, 12:36 UTC · re: Gergely Buday · lore

RE: git branch

Show 9 quoted lines

> From: gbuday@gmail.com
>
> > I'm not sure if I'm following you correctly, but with Git you need to
> > check out your branch after creating it. Run git checkout install_2.0
> > after you have created it.
>
> Yes, that sounds reasonable. I did not know it was necessary to "switch to it".
>
> - Gergely

Hi Gergely,

The way that git branches work is that they "point" at commits. When you do a "git commit", git updates the branch to point at the new commit you just created. In this way, you can have a multitude of branches and be working on only one at a time.

N.B. If you want to create a branch and "switch" (checkout) to it at once, you can pass the "-b" option to checkout, thus: "git checkout -b new-branch-name"; this will create a new branch named "new-branch-name" and immediately switch to it.

Tim.

() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments