はてなブックマーク

I’m ready to bet that setting up and deleting remote branches is something you do rarely enough that you always find yourself looking up the documentation. Or maybe it’s just me. Due to its roots, Git supports a wide array of usage scenarios for interacting with remote repositories, and we love it that way. It’s a big factor in the flexibility and power of the tool. However in simple scenarios, th

Git is one hell of a powertool. Like with any such tool, as soon as you get to know it enough, you start pushing the boundaries. Git gives you a lot of control over your repository: trivial branching and merging (even with long lived branches); rebasing as a cleaner alternative to merging; stashing aside your changes for a quick fix elsewhere; extracting logical, distinct commits from a multi-hour