Mixing
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.
git
asked yesterday
DDave
372315
add a comment |
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.
git
asked yesterday
DDave
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
add a comment |
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.
git
asked yesterday
DDave
372315
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
git
asked yesterday
DDave
372315
asked yesterday
DDave
372315
asked yesterday
DDave
372315
asked yesterday
DDave
372315
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
add a comment |
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
add a comment |
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.
answered yesterday
RomainValeri
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
add a comment |
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.
answered yesterday
RomainValeri
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
add a comment |
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.
answered yesterday
RomainValeri
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
add a comment |
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.
answered yesterday
RomainValeri
1,19911024
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.
answered yesterday
RomainValeri
1,19911024
answered yesterday
RomainValeri
1,19911024
answered yesterday
RomainValeri
1,19911024
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
add a comment |
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
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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