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
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 ...
Answer
#2: Post edited
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
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.