Explore >> Select a destination


You are here

jfr.im
| | www.paritybit.ca
10.5 parsecs away

Travel
| | I've recently overhauled a lot of the software I use which means I have a whole new set of configuration files for most of that software. I figured it would be a good time to change the way I manage these configuration files too.
| | bartlomiejmika.com
5.7 parsecs away

Travel
| | The purpose of this article is to help you setup a personal blog as quickly as possible. These are the instructions and notes Ive written down when setting up my site that Id like to share.
| | brandont.dev
6.1 parsecs away

Travel
| |
| | www.erikschierboom.com
89.0 parsecs away

Travel
| Introduction When using git, local branches can track remote branches that no longer exist (the remote branch is gone). To identify these branches, we first have to cleanup (prune) the remote's branches: $ git fetch -p From https://test.com - [deleted] (none) -> origin/disable-feature-x - [deleted] (none) -> origin/fix-typo - [deleted] (none) -> origin/grammar-fix In this case, three remote branches were deleted. Let's see if we have local branches that are tracking deleted branches: