The branches represent a pointer to a snapshot of a developer’s changes. Branches are an essential part of the everyday development process in Git. The git branch is available in most of the version control systems. This should do something close to what you’re looking for: git config -global is defining what action git push must take in case a refspec is not given. Have sublime automatically figure out the corresponding local branch for each $remote and call it $local, and then have the entry perform the git branch -f $local $remote command, for each entry.Įasiest way to make this happen is with git aliases & you’ll be able to use them on the command line as well.

Hell I’m not even sure plugins could do that - it all depends on how the API will be designed.

I guess the current menu modification functionality is not flexible enough for something like that as of now. I want to be able to right click the commit currently pointed at by the remote branch (or several remote branches), have sublime create separate menu entries for each remote branch (with $remote being the remote branch in each entry), have sublime automatically figure out the corresponding local branch for each $remote and call it $local, and then have the entry perform the git branch -f $local $remote command, for each entry. I’m looking for a kind of Commit.sublime-menu & Remote Branch.sublime-menu hybrid. I don’t really like the Location Bar and it’s closed 99% of the time for me. Your suggestion is great and it helps a bit but it’s not exactly what I wanted - I want to be able to do that from the commit tree directly. I didn’t know about the menu modifications feature of Sublime Merge, this makes it so much more powerful. Is there anything similar to this in Sublime Merge? (it resets the local branch and immediately checks it out meaning you go straight to the up-to-date commit) Reset local branch with the name: 'feature' The Git Extensions client has the following checkbox when you try to checkout a remote branch, which is exactly what I’m looking for: This means that in order to work on the latest version of feature, I have to look around the graph view, find the local feature branch which is several commits behind, check it out (which inconveniently changes my work-tree to some old version, potentially interfering with IDE’s), then merge/reset it to sync it with the up-to-date origin/feature branch.Īnother option I have is to delete the local feature branch and then use the option pictured above, but that’s a bit awkward. However, if a corresponding feature branch tracking origin/feature branch already exists (out of sync with the remote branch, some commits behind), this option doesn’t appear anymore. This option is very convenient - it creates a branch named feature tracking origin/feature and it performs a checkout of that branch automatically. When I right click a remote branch in the graph view, there’s this option: # Checkout the now up-to-date feature branch Basically I’m looking for the Sublime Merge equivalent of the two following CLI commands: # Reset 'feature' to 'origin/feature' without checkout

Checkout remote branch