If you committed on a completely different branch (e.g. Note that this solution only works if you’re ahead of your “base branch”. You’re now back on your feet, and you can keep working as if you never made the mistake in the first place. git reset -soft origin/masterĬheckout your feature branch. Reset master to its previous state, without touching the working copy (you don’t even need to stash your uncommitted changes, but you can if it makes you feel safer). Note that we’re not switching to the new branch, we’re still on master. This way your commit will remain accessible via the branch. Information: If a module throws an error during the scenario execution and there is no error handling route attached to the module, a default error handling. restore your master to it’s previous stateĬreate the feature branch pointing to your current commit.you have diverged from the central repo’s master branch, which will cause issues the next time you try to pull.you can’t publish your work, because the server will reject a push to master.
Now, let’s assume that your team follows this workflow, and you accidentally committed to master, because you forgot to create your feature branch before you started to work (happens to me all the time!).
#Fix typo mistake in old commit how to
Oh no, you just accidentally commited to master, when you were supposed to work on a feature branch! How to fix it? It’s actually pretty easy with Git!Ī common Git workflow nowadays is the “feature branch” workflow: you can’t push directly to the “main” branch (usually master, but it can be something else) instead you have to create a branch from master, commit to that branch, publish it and submit a pull request.
0 kommentar(er)
