gitflow pulling and work with remote branch











up vote
0
down vote

favorite












I'm using gitflow, and I changed of computer, my feature called 'migration' is showed like remote branch



git branch -a
* develop
master
remotes/origin/HEAD -> origin/develop
remotes/origin/develop
remotes/origin/feature/migration


what is the right way to pull that branch, and complete the work, then do commits and push. I was using gitkraken, but i feel have bugs when you are in complex scenaries and with more than one features open, do the things very automatically in the wrong way.










share|improve this question






















  • Possible duplicate of How do I check out a remote Git branch?
    – fredrik
    yesterday










  • the answer duplicate is confuse
    – DDave
    yesterday










  • the duplicate answer is very confused, i need only a clear answer
    – DDave
    yesterday















up vote
0
down vote

favorite












I'm using gitflow, and I changed of computer, my feature called 'migration' is showed like remote branch



git branch -a
* develop
master
remotes/origin/HEAD -> origin/develop
remotes/origin/develop
remotes/origin/feature/migration


what is the right way to pull that branch, and complete the work, then do commits and push. I was using gitkraken, but i feel have bugs when you are in complex scenaries and with more than one features open, do the things very automatically in the wrong way.










share|improve this question






















  • Possible duplicate of How do I check out a remote Git branch?
    – fredrik
    yesterday










  • the answer duplicate is confuse
    – DDave
    yesterday










  • the duplicate answer is very confused, i need only a clear answer
    – DDave
    yesterday













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm using gitflow, and I changed of computer, my feature called 'migration' is showed like remote branch



git branch -a
* develop
master
remotes/origin/HEAD -> origin/develop
remotes/origin/develop
remotes/origin/feature/migration


what is the right way to pull that branch, and complete the work, then do commits and push. I was using gitkraken, but i feel have bugs when you are in complex scenaries and with more than one features open, do the things very automatically in the wrong way.










share|improve this question













I'm using gitflow, and I changed of computer, my feature called 'migration' is showed like remote branch



git branch -a
* develop
master
remotes/origin/HEAD -> origin/develop
remotes/origin/develop
remotes/origin/feature/migration


what is the right way to pull that branch, and complete the work, then do commits and push. I was using gitkraken, but i feel have bugs when you are in complex scenaries and with more than one features open, do the things very automatically in the wrong way.







git






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked yesterday









DDave

372315




372315












  • Possible duplicate of How do I check out a remote Git branch?
    – fredrik
    yesterday










  • the answer duplicate is confuse
    – DDave
    yesterday










  • the duplicate answer is very confused, i need only a clear answer
    – DDave
    yesterday


















  • Possible duplicate of How do I check out a remote Git branch?
    – fredrik
    yesterday










  • the answer duplicate is confuse
    – DDave
    yesterday










  • the duplicate answer is very confused, i need only a clear answer
    – DDave
    yesterday
















Possible duplicate of How do I check out a remote Git branch?
– fredrik
yesterday




Possible duplicate of How do I check out a remote Git branch?
– fredrik
yesterday












the answer duplicate is confuse
– DDave
yesterday




the answer duplicate is confuse
– DDave
yesterday












the duplicate answer is very confused, i need only a clear answer
– DDave
yesterday




the duplicate answer is very confused, i need only a clear answer
– DDave
yesterday












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










Just git checkout feature/migration and it will create the branch locally then set up upstream.



You'll be able to work on it as usual, make changes, add, commit and push without additional steps.






share|improve this answer





















  • accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
    – DDave
    yesterday










  • No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
    – RomainValeri
    yesterday













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',
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%2f53372439%2fgitflow-pulling-and-work-with-remote-branch%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote



accepted










Just git checkout feature/migration and it will create the branch locally then set up upstream.



You'll be able to work on it as usual, make changes, add, commit and push without additional steps.






share|improve this answer





















  • accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
    – DDave
    yesterday










  • No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
    – RomainValeri
    yesterday

















up vote
0
down vote



accepted










Just git checkout feature/migration and it will create the branch locally then set up upstream.



You'll be able to work on it as usual, make changes, add, commit and push without additional steps.






share|improve this answer





















  • accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
    – DDave
    yesterday










  • No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
    – RomainValeri
    yesterday















up vote
0
down vote



accepted







up vote
0
down vote



accepted






Just git checkout feature/migration and it will create the branch locally then set up upstream.



You'll be able to work on it as usual, make changes, add, commit and push without additional steps.






share|improve this answer












Just git checkout feature/migration and it will create the branch locally then set up upstream.



You'll be able to work on it as usual, make changes, add, commit and push without additional steps.







share|improve this answer












share|improve this answer



share|improve this answer










answered yesterday









RomainValeri

1,19911024




1,19911024












  • accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
    – DDave
    yesterday










  • No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
    – RomainValeri
    yesterday




















  • accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
    – DDave
    yesterday










  • No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
    – RomainValeri
    yesterday


















accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
– DDave
yesterday




accort to duplicate question link, is not secure if there is more one remote branch, there is not better use the complete name ? something like: git checkout remotes/origin/feature/migration , so i'm sure ?
– DDave
yesterday












No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
– RomainValeri
yesterday






No, if you do that you won't create a local counterpart for the remote branch. You seem afraid of something but I can't figure out what.
– RomainValeri
yesterday




















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53372439%2fgitflow-pulling-and-work-with-remote-branch%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

'app-layout' is not a known element: how to share Component with different Modules

android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

WPF add header to Image with URL pettitions [duplicate]