There is more margin for error with this one. Have a look at git status before you commit to checking. Then create a new branch and check it out in one go and add and commit your changes again.īe careful with the add -A though as you may be adding unrelated uncommitted files and directories. Then undo the commits with git reset HEAD~Nwhere “N” is the number of commits you want to undo. Use git log to check how many commits you want to roll back. Make sure you are on the branch to which you have been committing. However, it means that all your commits are passed over to the new branch – though, of course, you should check your results before pushing up to your central repo, as it is slightly easier to get wrong. The second solution is a little more involved. The downside is, however, that you don’t get your original commit messages on the new branch, and all changes are applied as a single commit with a new commit message etc. The first solution is nice, simple and easy to apply without a relatively small margin for error. Modify refs manually for the master to point back to where you were and for your new branch ref to.
Undo commits on master, checkout new branch myfeature and commit all your changes as one commit.And secondly, you need to get your changes on that new branch. First of all, you need to revert the master back to where it originally was. Let’s say you committed to master, and you meant to commit to a new branch called “myfeature”. Well, this is Git we are talking about, so the good news is that it’s relatively straightforward.
0 kommentar(er)
