Explore >> Select a destination


You are here

betterdev.blog
| | mislav.net
3.7 parsecs away

Travel
| | Some hidden gems of git version control
| | misha.brukman.net
2.9 parsecs away

Travel
| | Useful Git aliases for streamlined workflows.
| | andre.arko.net
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...
| | www.cesarsotovalero.net
18.5 parsecs away

Travel
| Git is the go-to version control system in software development, created by Linus Torvalds in 2005 for Linux kernel development. It's now an indispensable tool for tracking project history and managing versions. This post covers the key Git commands you need to streamline your development workflow.