Explore >> Select a destination
|
You are here 
|
haacked.com | ||
| | | | |
betterdev.blog
|
|
| | | | | No upstream branch error from Git push command may seem strange. Here I explain it and show how to simplify first branch push to avoid it. | |
| | | | |
www.karl.berlin
|
|
| | | | | ||
| | | | |
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: | |
| | | | |
zwischenzugs.com
|
|
| | | Recently, while showing someone at work a useful Git 'trick', I was asked "how many ways are there to undo a bad change in Git?". This got me thinking, and I came up with a walkthrough similar to the ones I use in my book to help embed key Git concepts and principles. There's many... | ||
