Deleting commits from a remote repository in Git
Sometimes when using Git, we realize that a commit was wrong and needs to be removed. The reason may be that the customer does not want to use this feature in the product.
Either we introduced a bug, or we need to work on it again because we already committed a bad implementation.
This article will discuss how we can delete local and remote repositories and clean up all of them using Git commands.
In Git, we can remove commits through two different processes. These processes depend on the changes, whether they have been pushed to a remote branch or not.
Deleting commits from a local repository in Git
If our changes have not yet been pushed to the remote repository, we can delete the most recent commit locally with the following command:
git reset --hard HEAD~1
The above mentioned command will discard all changes made in the folder (working tree) and HEAD
move to HEAD
the latest commit before .
If we want to remove the commits before a specific commit, we will run git log
to search for the specific commit id. After that, we will remove those commits using the below mentioned commands:
git reset --hard <sha1-commit-id>
This command mentioned earlier will discard all changes made in the working tree and HEAD
move to the commit of our choice.
Deleting commits from a remote repository in Git
If we want to remove a commit from the remote repository, we'll make a 强制推送
new HEAD
commit. Or, if we've already pushed changes to the remote repository, we'll run the following command:
git push origin HEAD --force
If someone else pulls this branch, then it's best to start a new branch; otherwise, it will merge it into their work, in which case we need to push back to the same branch again.
This will remove that commit from both the local and remote repositories. If we need to remove it only from the remote and not from the local, then we will execute the below mentioned command:
git push origin +HEAD^:branch_name
Before executing these commands, we should take another look at it, as it will delete all of our working directory changes.
After deleting it, if we want to search for that commit again, it will preferably appear in <git reflog>
, unless our repository has been garbage collected.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git installation and establishment of local warehouse service
Publish Date:2025/04/05 Views:89 Category:Git
-
Git is a distributed version control system: the client does not only extract the latest version of the file snapshot, but also completely mirrors the original code repository. It has the following advantages: a. Since every extraction oper
git remote operation——multiple remote repositories for one project
Publish Date:2025/04/05 Views:131 Category:Git
-
Multiple remote repositories for a git project In our git project, the command to operate the remote repository information is $ git remote # 查看当前所有的远程仓库的名称 $ git remote -v # 查看远程仓库的名称和远程仓
Git cherry pick command usage
Publish Date:2025/04/05 Views:190 Category:Git
-
git cherry-pick is a powerful command that allows us to select an arbitrary Git commit by reference and attach it to the HEAD of the current working branch. Cherry picking is the act of picking a commit from one branch and applying it to an
Comparison between Git merge and Git rebase
Publish Date:2025/04/05 Views:171 Category:Git
-
The git rebase command may seem like Git wizardry to beginners, but if used carefully, it can actually make life easier for your development team. In this article, we compare git rebase with the related git merge command and identify all th
How to fix Git error Error: src refspec master does not match any
Publish Date:2025/04/05 Views:124 Category:Git
-
When using Git, we may encounter the error "src refspace master does not match any". Here's what the error means and how to fix it. What does src refspec master does not match any Mean in Git mean? We may encounter this error when we try to
Rebase local branch when pulling changes from remote repository branch in Git
Publish Date:2025/04/05 Views:144 Category:Git
-
This article will cover the basics of rebasing your local branch when pulling changes from a remote repository branch in Git. We use the version control system Git to track changes made to files. We commit changes in a local branch in our l
Undo Git Stash
Publish Date:2025/04/04 Views:187 Category:Git
-
This article explains how to make and save changes to a repository. Git allows you to save changes locally and push them to a server when needed. In Git, we don't use the term save , but commit . We use git add , git commit , and git stash
View a list of cache entries in Git
Publish Date:2025/04/04 Views:59 Category:Git
-
We often need to pause our work and focus on something else in our development environment. Therefore, we may need to temporarily save our current work and focus on a different one. We may want to resume our original work later. git stash T
Git stores specific files
Publish Date:2025/04/04 Views:115 Category:Git
-
This article will cover storing changes to only specific files in Git. In Git, when we make some changes in our working tree, we may have some changes which may or may not be staged in our local repo. We may now wish to save these changes f