/explore
|
You are here 
|
haacked.com | ||
| | | | |
www.karl.berlin
|
|
| | | | | ||
| | | | |
bengarvey.com
|
|
| | | | | [AI summary] A practical guide to a simplified, safe workflow for managing version control with Git. | |
| | | | |
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: | |
| | | | |
javier.io
|
|
| | | how to keep your Git-Fork up to date | ||
