Skip to contentSkip to conversation

How to create branches above master

DISCUSSION Bharani Prasad 3 participants 3 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

I am using git-repository along with gerrit server for code review, I want to create branches called "Integration" branch & "Release" branch

I got different projects which I need to integrate in "integrate" branch and give it to testing and once the bugs are fixed it should go to "release" branch.

Currently we are using master and private branches...

Please do help me with this issue, as it is critical...

And also can you suggest me what can I use for Continuous build system in Linux Fedora

Signature · 2 lines
View this message in context: http://old.nabble.com/How-to-create-branches-above-master-tp29342864p29342864.html
Sent from the git mailing list archive at Nabble.com.
#1 lore raw
Quoted 2 lines · Bharani Prasad

I am using git-repository along with gerrit server for code review, I want to create branches called "Integration" branch & "Release" branch

What's stopping you? See git-checkout(1) for how to create branches.

Quoted 3 lines

I got different projects which I need to integrate in "integrate" branch and give it to testing and once the bugs are fixed it should go to "release" branch.

See git-merge(1) et al for how to merge branches.

Quoted 1 line

Please do help me with this issue, as it is critical...

Please ask more specific questions if you'd like useful answers.

Quoted 2 lines

And also can you suggest me what can I use for Continuous build system in Linux Fedora

Buildbot? Any of the intersection between Google's results for "continuous integration" and "git". They're all good.

#2 lore raw

To Bharani: It sounds like you are using one repository for multiple projects. Git doesn't handle this use case very well.

Quoted 5 lines · Ævar Arnfjörð Bjarmason
Quoted 3 lines

I got different projects which I need to integrate in "integrate" branch and give it to testing and once the bugs are fixed it should go to "release" branch.

See git-merge(1) et al for how to merge branches.

I think he might need git-cherrypick for this use-case since you don't want to merge all of integration into release.