|
You are here |
cmetcalfe.ca | ||
| | | | |
www.erikschierboom.com
|
|
| | | | | 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: | |
| | | | |
cassidoo.co
|
|
| | | | | If you're tired of your git branches being alphabetically sorted, you can change that! | |
| | | | |
haacked.com
|
|
| | | | | A git alias to clean up gone branches. Even ones that have been squashed and merged. | |
| | | | |
blog.foletta.net
|
|
| | | [AI summary] This technical article explores the internal data structures and fundamental constructs of Git, explaining how it manages source control through blobs, trees, commits, branches, and the index. | ||