JIYIK CN >

This article explains how to reset commits in Git that have not yet been pushed to a remote repository. Git is a version control system that we use to track changes made to files in a project directory.

In Git, commits are used to track changes made to files. Sometimes, we might commit changes to a file locally, and then we might feel that those changes are no longer relevant.

We now want to reset this commit instead of pushing it to the remote repository. We can use git resetthe command to complete the task of resetting a commit that has not yet been pushed to the remote.

Undo commits before pushing to remote repository in Git

We use Git in a collaborative development environment to track changes made to files. Git uses commits to accomplish the task of tracking changes to files.

When we are happy with the changes we made to the files, we commit the changes to the project's Git repository. In the basic Git workflow, once we have tested and finished with the changes, we add the changes to the staging area. To do this, we use git addthe command.

After adding the changes to the staging area, we now proceed to commit the changes to our Git repository. We use the command git committo commit the changes.

Each commit is used to record a snapshot of the repository state along with a name, timestamp, and message. When we git commitcommit changes using the command, these changes are committed to the local Git repository.

This local repository is associated with the remote Git repository. We then proceed to push the commits from the local Git repository to the remote repository. We use git pushthe command to achieve this.

Sometimes, before pushing commits to the remote repository, we may feel that the current commits in the local repository are no longer needed and we want to discard them.

Therefore, to discard the commits in the local repository, we can use git resetthe command. Suppose we have the following commit history in our Git repository.

$ git log --oneline
453dcfc (HEAD -> master) minor change
bea3aac (origin/master, origin/HEAD) some change
b14f387 Other change
...

In the commit history, a commit 453dcfcis in the local Git repository but not yet in the remote repository. The previous commit is also in the remote repository.

Therefore, to discard commits that exist in the local repository but have not been pushed to the remote repository, we can execute git resetthe command as shown below.

$ git reset --soft HEAD~1

The above git resetcommand HEADresets the current . The command with --softthe option git resetdoes not touch the staging area and the working tree.

It saves all our changed files as 要提交的更改, just git statusas said, as shown below.

$ git status
On branch master
Your branch is up to date with 'origin/master'.

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   README.md

We can now re-examine the commit history and observe that commit 453dcfcno longer exists.

$ git log --oneline
bea3aac (origin/master, origin/HEAD) some change
b14f387 Other change
...

We have shown how to reset commits in Git that have not yet been pushed to a remote repository.