revert a feature in git for temporary
up vote
0
down vote
favorite
I pushed my latest feature but I found there's a critical bug. I want to rollback. So I do git checkout 12345 I got detached HEAD, I don't know how to proceed. Is checkout previous commit even a proper way to revert a feature?
git github
asked Nov 11 at 2:09
Hoknimo
456
add a comment |
up vote
0
down vote
favorite
I pushed my latest feature but I found there's a critical bug. I want to rollback. So I do git checkout 12345 I got detached HEAD, I don't know how to proceed. Is checkout previous commit even a proper way to revert a feature?
git github
asked Nov 11 at 2:09
Hoknimo
456
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I pushed my latest feature but I found there's a critical bug. I want to rollback. So I do git checkout 12345 I got detached HEAD, I don't know how to proceed. Is checkout previous commit even a proper way to revert a feature?
git github
asked Nov 11 at 2:09
Hoknimo
456
I pushed my latest feature but I found there's a critical bug. I want to rollback. So I do git checkout 12345 I got detached HEAD, I don't know how to proceed. Is checkout previous commit even a proper way to revert a feature?
git github
git github
asked Nov 11 at 2:09
Hoknimo
456
asked Nov 11 at 2:09
Hoknimo
456
asked Nov 11 at 2:09
Hoknimo
456
asked Nov 11 at 2:09
Hoknimo
456
asked Nov 11 at 2:09
Hoknimo
456
456
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02
add a comment |
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Since you've already pushed your changes, your best course of action would be to create a new commit that undoes the unwanted commit. You can do this by using the git-revert command:
git revert <hash of unwanted commit>
Then, push this new commit.
Regarding your detached HEAD state, the HEAD reference is unique to your local repository. By checking out the last good commit, you've rolled back your local repository, however the the server and any other users would not see this. You can move the branch back to a good commit by using git reset --hard <hash of last good commit>, however this rewrites history. If you were to push this (using a force push), the server would probably complain and other users of the repository would encounter conflicts because their local history no longer matches what's on the server.
answered Nov 11 at 3:05
Seth
1158
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
Since you've already pushed your changes, your best course of action would be to create a new commit that undoes the unwanted commit. You can do this by using the git-revert command:
git revert <hash of unwanted commit>
Then, push this new commit.
Regarding your detached HEAD state, the HEAD reference is unique to your local repository. By checking out the last good commit, you've rolled back your local repository, however the the server and any other users would not see this. You can move the branch back to a good commit by using git reset --hard <hash of last good commit>, however this rewrites history. If you were to push this (using a force push), the server would probably complain and other users of the repository would encounter conflicts because their local history no longer matches what's on the server.
answered Nov 11 at 3:05
Seth
1158
add a comment |
up vote
0
down vote
Since you've already pushed your changes, your best course of action would be to create a new commit that undoes the unwanted commit. You can do this by using the git-revert command:
git revert <hash of unwanted commit>
Then, push this new commit.
Regarding your detached HEAD state, the HEAD reference is unique to your local repository. By checking out the last good commit, you've rolled back your local repository, however the the server and any other users would not see this. You can move the branch back to a good commit by using git reset --hard <hash of last good commit>, however this rewrites history. If you were to push this (using a force push), the server would probably complain and other users of the repository would encounter conflicts because their local history no longer matches what's on the server.
answered Nov 11 at 3:05
Seth
1158
add a comment |
up vote
0
down vote
up vote
0
down vote
Since you've already pushed your changes, your best course of action would be to create a new commit that undoes the unwanted commit. You can do this by using the git-revert command:
git revert <hash of unwanted commit>
Then, push this new commit.
Regarding your detached HEAD state, the HEAD reference is unique to your local repository. By checking out the last good commit, you've rolled back your local repository, however the the server and any other users would not see this. You can move the branch back to a good commit by using git reset --hard <hash of last good commit>, however this rewrites history. If you were to push this (using a force push), the server would probably complain and other users of the repository would encounter conflicts because their local history no longer matches what's on the server.
answered Nov 11 at 3:05
Seth
1158
Since you've already pushed your changes, your best course of action would be to create a new commit that undoes the unwanted commit. You can do this by using the git-revert command:
git revert <hash of unwanted commit>
Then, push this new commit.
Regarding your detached HEAD state, the HEAD reference is unique to your local repository. By checking out the last good commit, you've rolled back your local repository, however the the server and any other users would not see this. You can move the branch back to a good commit by using git reset --hard <hash of last good commit>, however this rewrites history. If you were to push this (using a force push), the server would probably complain and other users of the repository would encounter conflicts because their local history no longer matches what's on the server.
answered Nov 11 at 3:05
Seth
1158
edited Nov 11 at 3:10
answered Nov 11 at 3:05
Seth
1158
answered Nov 11 at 3:05
Seth
1158
answered Nov 11 at 3:05
Seth
1158
1158
add a comment |
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%2f53245245%2frevert-a-feature-in-git-for-temporary%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
git-tower.com/learn/git/faq/detached-head-when-checkout-commit. Checking out does not revert anything, but you can continue committing from it to act as if the feature never happened.
– evolutionxbox
Nov 11 at 2:15
Possible duplicate of Delete commits from a branch in Git
– phd
Nov 11 at 10:02
stackoverflow.com/search?q=%5Bgit%5D+undo+pushed+commits
– phd
Nov 11 at 10:02