/explore
|
You are here 
|
betterdev.blog | ||
| | | | |
mislav.net
Some hidden gems of git version control |
|
| | | | | ||
| | | | |
andre.arko.net
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... |
|
| | | | | ||
| | | | |
felipec.wordpress.com
Probably one of most powerful and under-utilized concepts of git is the upstream tracking branch, and to be honest it probably was too difficult to use properly in the past, but not so much any more. Here I'll try to explain what it is, and how you can take the most advantage out of it.... |
|
| | | | | ||
| | | | |
bengarvey.com
[AI summary] A practical guide to a simplified, safe workflow for managing version control with Git. |
|
| | | |||
