![sublime merge rebase sublime merge rebase](https://forum.sublimetext.com/uploads/default/original/3X/2/a/2ab03ddbc703271b600f34d13a7676f573d1bdde.png)
Omit this flag you want Git to reuse the Sublime window you already have open. Sublime Merge is described as fast and intuitive git client built on the same performant platform as Sublime Text and is a Git Client in the development. -n tells Git to open a new editor window.core.editor is the setting which tells Git which editor to use.git config is used to set global and repository settings.Open a command prompt and type the following command: git config -global core.editor "'' -n -w"įor Sublime Text on Windows, this is the command: git config -global core.editor "'C:\Program Files\Sublime Text 3\subl.exe' -n -w"
SUBLIME MERGE REBASE HOW TO
VIM is a fine editor if you know how to use it, but I prefer to use Sublime Text. It is interactive because Git will open a text editor to ask for input. It is very important to only rebase branches which you haven't shared with others yet. You can commit exactly what you want using line-by-line and Hunk staging. You may want to squash some commits or alter your commit messages for example. Unmatched Performance Sublime Merge is a fast cross-platform GUI toolkit that also features an unmatched syntax highlighting engine and a custom high performance Git reading library. Why would anyone want to do this? Rebasing can be used to clean up your commit history on a branch before pushing it. I won't write too much about it here, as others have covered it already, but in essence it allows you to re-write the history of your repository. Rebasing is a powerful and advanced Git concept. Others are config changes I like to make to my environment. Some are commands I use, but not often enough to remember the syntax. This is the overdue second post, in my series of Git tips for both new and experienced Git users. Menu Git Tips #2 - Change editor for interactive Git rebase 08 March 2016 on git, git-tips 0 Comments