Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

81%
+7 −0
Q&A How to revert main branch to an earlier commit in git?

With git reset, but first, you may want to save the current state in another branch: $ git switch main $ git branch backup-of-main Now the (perhaps messed up) state is safely stored in branch ...

posted 7mo ago by Iizuki‭  ·  edited 7mo ago by Alexei‭

Answer
#2: Post edited by user avatar Alexei‭ · 2023-10-10T06:58:41Z (7 months ago)
inlined the link for the Git documentation + minor fixes
  • With `git reset`, but first you may want to save the current state in another branch:
  • ```bash
  • $ git switch main
  • $ git branch backup-of-main
  • ```
  • Now the (perhaps messed up) state is safely stored in branch `backup-of-main`, and you can always just switch back to it and have another swing.
  • To move `main` to an earlier commit: [[1]](https://git-scm.com/docs/git-reset#Documentation/git-reset.txt-emgitresetemltmodegtltcommitgt)
  • ```bash
  • $ git switch main
  • $ git reset --hard <commit-hash>
  • ```
  • Now you might still run into issues when pushing main to a remote which has already seen the more futuristic states. In this case you need to force push:
  • ```bash
  • $ git push --force
  • ```
  • When you are _absolutely sure_ that it worked out as you planned, you may consider removing the `backup-of-main` branch. See [this question](https://software.codidact.com/posts/289829) for how.
  • With `git reset`, but first, you may want to save the current state in another branch:
  • ```bash
  • $ git switch main
  • $ git branch backup-of-main
  • ```
  • Now the (perhaps messed up) state is safely stored in branch `backup-of-main`, and you can always just switch back to it and have another swing.
  • To move `main` to [an earlier commit](https://git-scm.com/docs/git-reset#Documentation/git-reset.txt-emgitresetemltmodegtltcommitgt):
  • ```bash
  • $ git switch main
  • $ git reset --hard <commit-hash>
  • ```
  • You might still run into issues when pushing `main` to a remote that has already seen the more futuristic states. In this case, you need to force push:
  • ```bash
  • $ git push --force
  • ```
  • When you are _absolutely sure_ that it worked out as you planned, you may consider removing the `backup-of-main` branch. See [this question](https://software.codidact.com/posts/289829) for how.
#1: Initial revision by user avatar Iizuki‭ · 2023-10-09T12:54:54Z (7 months ago)
With `git reset`, but first you may want to save the current state in another branch:

```bash
$ git switch main
$ git branch backup-of-main
```
Now the (perhaps messed up) state is safely stored in branch `backup-of-main`, and you can always just switch back to it and have another swing.

To move `main` to an earlier commit: [[1]](https://git-scm.com/docs/git-reset#Documentation/git-reset.txt-emgitresetemltmodegtltcommitgt)
```bash
$ git switch main
$ git reset --hard <commit-hash>
```

Now you might still run into issues when pushing main to a remote which has already seen the more futuristic states. In this case you need to force push:
```bash
$ git push --force
```

When you are _absolutely sure_ that it worked out as you planned, you may consider removing the `backup-of-main` branch. See [this question](https://software.codidact.com/posts/289829) for how.