/explore
|
You are here 
|
felipec.wordpress.com | ||
| | | | |
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... | |
| | | | |
betterdev.blog
|
|
| | | | | No upstream branch error from Git push command may seem strange. Here I explain it and show how to simplify first branch push to avoid it. | |
| | | | |
jinyuz.dev
|
|
| | | There was a pull request on GitHub and it contains a feature I wanted to test. I didn't know how to test it locally. Should I just copy the changes to my local since the changes weren't that big? But what if it was? Luckily, I found some answers by googling and decided to write it up for future reference. Git provides a command for it and here is the sample syntax | ||
