Explore >> Select a destination
|
You are here 
|
haacked.com | ||
| | | | |
blog.danskingdom.com
|
|
| | | | | Git is super powerful, but can also be confusing, especially when using the command line interface (CLI). It has so many commands, and I only regularly use a handful of them. | |
| | | | |
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: | |
| | | | |
bengarvey.com
|
|
| | | | | [AI summary] The article provides a minimalist approach to using Git for version control, focusing on essential commands like checkout, push, pull, commit, and branch management. | |
| | | | |
gist.github.com
|
|
| | | GitHub Gist: instantly share code, notes, and snippets. | ||
