Removing unpushed commits in Git
This article will teach you how to delete unpushed commits in Git.
Git is used in collaborative development environments to track changes made to files in a project directory. Git uses commits to track changes to local and remote Git repositories.
From time to time, one may wish to remove unpushed commits from a local Git repository.
Use git reset
the command to remove unpushed commits. We will illustrate this with an example.
Use git reset
the command to delete unpushed commits in Git
Whenever we want to commit changes to our project directory, we can commit the changes using the git add
and git commit
commands.
When you use git commit
the command, commits are created in the local Git repository. We can then use git push
the command to push the commits in the local Git repository to the remote Git repository.
Sometimes, we may realize that we do not want to push the commit to the remote repository, but only commit to the local repository. In this case, we can use git reset
the command to cancel the commit or delete the last commit in the local Git repository.
git reset
Is a command used to undo local changes to the state of a Git repository.
Assume we have made changes to our working directory. We can git status
view the status of the changes using the command.
$ git status
On branch main
Your branch is up to date with 'origin/main'.
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
(commit or discard the untracked or modified content in submodules)
modified: mynotes.txt
We can see that mynotes.txt
the file has been modified and is eligible for commit.
To commit our modifications, we need to first git add
add the changes to the staging index of our local Git repository using the command. We must run the command as follows git add
.
$ git add .
$ git status
On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: mynotes.txt
So when using git status
the command we can see that the changes have now been staged.
We can commit the changes to our local Git repository. We have to use git commit
the command to create a commit for the staged changes.
We run git commit
the command as follows.
$ git commit -m "updated mynotes"
[main e1b08a5] updated mynotes
1 file changed, 1 insertion(+)
Now, let's run git status
the command again to check the status.
$ git status
On branch main
Your branch is ahead of 'origin/main' by 1 commit.
(use "git push" to publish your local commits)
We can now see that the local branch in our local repository is origin/main
one commit ahead of the remote Git repository branch.
We can use git push
the command to push the commits to the remote Git repository. But instead of doing that, we use git reset
the command to delete the unpushed commits as shown below.
$ git reset --soft HEAD~1
The command with --soft
the -p option git reset
removes unpushed commits from the local Git repository, but keeps local changes. HEAD~1
Specifying git reset
-p to remove only the last commit removes the last commit.
We will now run git status
to check the status of the repository as shown below.
$ git status
On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: mynotes.txt
So we can see that the unpushed commits are no longer there. However, the modifications are still in progress.
Using --hard
the -p option instead of --soft
the -p command option and git reset
the -p command will remove HEAD~1
the most recent commit specified by -p and complete your local changes.
We can --hard
run git reset
the command with the -p option.
$ git reset --hard HEAD~1
This will also remove untracked files or directories and tracked modifications. So use it with caution otherwise we may lose all the work we have done.
Therefore, we learned to delete unpushed commits in our local Git repository.
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