Fastest way to migrate Gitlab branches to another project












0















We are having a project with around 1000 Gitlab branches.



We would like to move around 300 existing branches to another existing ( completely unrelated ) project.



What is the fastest and efficient way to do it ?










share|improve this question

























  • "Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

    – kowsky
    Nov 20 '18 at 8:42













  • I have updated the question. Thanks for input.

    – Yuvraj Patil
    Nov 20 '18 at 9:04






  • 1





    You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

    – clmno
    Nov 20 '18 at 10:03
















0















We are having a project with around 1000 Gitlab branches.



We would like to move around 300 existing branches to another existing ( completely unrelated ) project.



What is the fastest and efficient way to do it ?










share|improve this question

























  • "Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

    – kowsky
    Nov 20 '18 at 8:42













  • I have updated the question. Thanks for input.

    – Yuvraj Patil
    Nov 20 '18 at 9:04






  • 1





    You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

    – clmno
    Nov 20 '18 at 10:03














0












0








0








We are having a project with around 1000 Gitlab branches.



We would like to move around 300 existing branches to another existing ( completely unrelated ) project.



What is the fastest and efficient way to do it ?










share|improve this question
















We are having a project with around 1000 Gitlab branches.



We would like to move around 300 existing branches to another existing ( completely unrelated ) project.



What is the fastest and efficient way to do it ?







git gitlab git-branch






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 20 '18 at 9:03







Yuvraj Patil

















asked Nov 20 '18 at 6:51









Yuvraj PatilYuvraj Patil

9061425




9061425













  • "Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

    – kowsky
    Nov 20 '18 at 8:42













  • I have updated the question. Thanks for input.

    – Yuvraj Patil
    Nov 20 '18 at 9:04






  • 1





    You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

    – clmno
    Nov 20 '18 at 10:03



















  • "Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

    – kowsky
    Nov 20 '18 at 8:42













  • I have updated the question. Thanks for input.

    – Yuvraj Patil
    Nov 20 '18 at 9:04






  • 1





    You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

    – clmno
    Nov 20 '18 at 10:03

















"Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

– kowsky
Nov 20 '18 at 8:42







"Another project", meaning an completely unrelated project or a fork of the other project? Do you mean to move commits or just create branches with the same names? You shouls elaborate on what exactly you want to do to make your question easier to answer.

– kowsky
Nov 20 '18 at 8:42















I have updated the question. Thanks for input.

– Yuvraj Patil
Nov 20 '18 at 9:04





I have updated the question. Thanks for input.

– Yuvraj Patil
Nov 20 '18 at 9:04




1




1





You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

– clmno
Nov 20 '18 at 10:03





You could fork it and then manually delete the branches you don't need. (could also write a script to do it.). You have to fork because that's the only way to clone the repo into someone else's ownership. And you need the git histor, so..

– clmno
Nov 20 '18 at 10:03












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53387675%2ffastest-way-to-migrate-gitlab-branches-to-another-project%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53387675%2ffastest-way-to-migrate-gitlab-branches-to-another-project%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

MongoDB - Not Authorized To Execute Command

Npm cannot find a required file even through it is in the searched directory

in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith