Menu
Did anyone managed to make an interactive rebase with Git Extensions ?
Option is available when rebasing, but whenever I selected the last n commits, select "interactive" in the rebase window, the editor pops up with "noop" comment instead of the commits lines.
Where am I wrong ?
866
You can run rebase interactively by adding the -i option to git rebase . You must indicate how far back you want to rewrite commits by telling the command which commit to rebase onto. Remember again that this is a rebasing command — every commit in the range HEAD~3..
Instead of blindly moving all of the commits to the new base, interactive rebasing gives you the opportunity to alter individual commits in the process. This lets you clean up history by removing, splitting, and altering an existing series of commits. It's like Git commit --amend on steroids.
For each change you make, you'll need to perform a new commit, and you can do that by entering the git commit --amend command. When you're finished making all your changes, you can run git rebase --continue . As before, Git is showing the commit message for you to edit.
Locate the commit you want to revert in the Log tab of the Git tool window Alt+9 , right-click it and select Revert Commit from the context menu. This option is also available from the context menu of a commit in the file History view. The Commit Changes dialog will open with an automatically generated commit message.
By default, Git extensions sets the branch to rebase against to the branch you are currently working on. So, unless you change that, there is nothing to do and you get this 'noop' message. You have to rebase against something that is not your current HEAD. Either that is some number of commits back from your head (eg HEAD~4) or the origin's version of your branch (eg: origin/master) or a specific named commit.
91
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
