/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 betterdev.blog
Simpler Git branch first push with no more errors | Better Dev
| | andre.arko.net
Track remote git branches with ease
2.2 parsecs away

Travel
| | tl;dr # ~/.gitconfig [aliases] track = "!f(){ branch=$(git name-rev --name-only HEAD); cmd=\"git branch --set-upstream $branch ${1:-origin}/${2:-$branch}\"; echo $cmd; $cmd; }; f" The problem Git is really great. That said, I find myself frequently annoyed by trying to manage upstream tracking branches. If you're creating a new branch for the first time, it's incredibly easy because git does the work for you. If you already have a branch, though, and you're trying to change the upstream branch, it's incredibly annoying. I expect to be able to use the same arguments that I use with git pull. That means I invoke git branch --set-upstream with invalid arguments, get an error message, start to read the git branch manpage, give up, and then edit .git/config direc...
| | vladimirzdrazil.com
Git tips and tricks | Vladimír Zdra?il
3.3 parsecs away

Travel
| | A collection of Git tips and tricks you might not know.
| | mislav.net
A few git tips you didn't know about
3.7 parsecs away

Travel
| | Some hidden gems of git version control
| | dev.clintonblackburn.com
git remaster | Clinton Blackburn
17.5 parsecs away

Travel
| I sometimes work across multiple branches for a variety of reasons, but usually when breaking up larger changes into smaller chunks. Sometimes I want to rebase these smaller chunks on my master branch. This usually results in the following series of commands: