Remove commit of github thoroughly
I know there are thousands of threads for this question, but I still can't find out a correctly way to remove commit thoroughly.
Yesterday, my friend send me a message,
"Hey guy, something interesting will happen if you run
git commit --amend --no-edit --date="Fri Nov 6 20:00:00 2015 -0600"
"
I did, and push it, then here is my github......The timeline is weird, so I try git reset --hard HEAD^ and push force, the commit disappeared, but the timeline not reverts.
So my question is, how to delete this commit thoroughly to restore overview to its original state.
git github
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
add a comment |
I know there are thousands of threads for this question, but I still can't find out a correctly way to remove commit thoroughly.
Yesterday, my friend send me a message,
"Hey guy, something interesting will happen if you run
git commit --amend --no-edit --date="Fri Nov 6 20:00:00 2015 -0600"
"
I did, and push it, then here is my github......The timeline is weird, so I try git reset --hard HEAD^ and push force, the commit disappeared, but the timeline not reverts.
So my question is, how to delete this commit thoroughly to restore overview to its original state.
git github
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
add a comment |
I know there are thousands of threads for this question, but I still can't find out a correctly way to remove commit thoroughly.
Yesterday, my friend send me a message,
"Hey guy, something interesting will happen if you run
git commit --amend --no-edit --date="Fri Nov 6 20:00:00 2015 -0600"
"
I did, and push it, then here is my github......The timeline is weird, so I try git reset --hard HEAD^ and push force, the commit disappeared, but the timeline not reverts.
So my question is, how to delete this commit thoroughly to restore overview to its original state.
git github
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
I know there are thousands of threads for this question, but I still can't find out a correctly way to remove commit thoroughly.
Yesterday, my friend send me a message,
"Hey guy, something interesting will happen if you run
git commit --amend --no-edit --date="Fri Nov 6 20:00:00 2015 -0600"
"
I did, and push it, then here is my github......The timeline is weird, so I try git reset --hard HEAD^ and push force, the commit disappeared, but the timeline not reverts.
So my question is, how to delete this commit thoroughly to restore overview to its original state.
git github
git github
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
asked Nov 28 '18 at 0:23
orzorzorzorzorzorzorzorz
336
336
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you managed to revert the commit but your GitHub profile is not yet updated to reflect this, then give it some time. Usually, it takes a while (up to a day) for GitHub to update some stuff. I had a similar experience where some statistics on GitHub were out-of-sync and it took up to a day in my case to sync.
Edit:
The OP figured out that correcting the error locally, deleting the repo from GitHub and reuploading it fixed the issue.
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
|
show 2 more comments
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
});
}
});
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%2f53510279%2fremove-commit-of-github-thoroughly%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
If you managed to revert the commit but your GitHub profile is not yet updated to reflect this, then give it some time. Usually, it takes a while (up to a day) for GitHub to update some stuff. I had a similar experience where some statistics on GitHub were out-of-sync and it took up to a day in my case to sync.
Edit:
The OP figured out that correcting the error locally, deleting the repo from GitHub and reuploading it fixed the issue.
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
|
show 2 more comments
If you managed to revert the commit but your GitHub profile is not yet updated to reflect this, then give it some time. Usually, it takes a while (up to a day) for GitHub to update some stuff. I had a similar experience where some statistics on GitHub were out-of-sync and it took up to a day in my case to sync.
Edit:
The OP figured out that correcting the error locally, deleting the repo from GitHub and reuploading it fixed the issue.
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
|
show 2 more comments
If you managed to revert the commit but your GitHub profile is not yet updated to reflect this, then give it some time. Usually, it takes a while (up to a day) for GitHub to update some stuff. I had a similar experience where some statistics on GitHub were out-of-sync and it took up to a day in my case to sync.
Edit:
The OP figured out that correcting the error locally, deleting the repo from GitHub and reuploading it fixed the issue.
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
If you managed to revert the commit but your GitHub profile is not yet updated to reflect this, then give it some time. Usually, it takes a while (up to a day) for GitHub to update some stuff. I had a similar experience where some statistics on GitHub were out-of-sync and it took up to a day in my case to sync.
Edit:
The OP figured out that correcting the error locally, deleting the repo from GitHub and reuploading it fixed the issue.
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
edited Mar 5 at 14:18
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
answered Nov 28 '18 at 0:34
RafaelRafael
3,15032234
3,15032234
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
|
show 2 more comments
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
This does not overwrite a previous commit. In fact, nothing can overwrite a previous commit. The advice to wait is, however, correct.
– torek
Nov 28 '18 at 0:46
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Right: what you're doing is replacing commits with new-and-improved versions. You then have to wait for GitHub to scan the replacements and update their other data. This is important, because anyone else who has the old commit, still has the old commit: you can't make them remove it. (They can remove it voluntarily, and usually will semi-automatically, when they update their clone.)
– torek
Nov 28 '18 at 0:51
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Yes. I just removed the statement entirely as it's not relevant in this specific question. Thanks for clarifying this, however, torek. (You are right as GitHub suggest that script only if you are alone on that repo.)
– Rafael
Nov 28 '18 at 0:52
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Thanks for answer, but almost half a year has passed, it didn't update at all...
– orzorzorzorz
Mar 5 at 14:03
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
Finally, I remove the repo, and then push it again, and then, it seems work well.
– orzorzorzorz
Mar 5 at 14:06
|
show 2 more comments
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.
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%2f53510279%2fremove-commit-of-github-thoroughly%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
