-
Have you ever tried to find a bug that only exists in staging, and no one knows why? That’s not nice at all.
-
It’s easy to check out new branches in Git. We’re moving forward with main and leaving master for the reflog.
-
Improve your everyday git workflows by automating the boring stuff.
-
It’s not always obvious what changed in your code after a git rebase. This tool makes changes more visible and helps you undo them if needed.
-
git rebase –onto is a useful tool for rebasing your branch off of another branch that has itself been rebased or had its history rewritten.
-
My workflow usually involves squashing many commits into a single one. But sometimes, the workflow calls for the opposite action – splitting a single commit into many. This is how I do it.
-
Don’t let your git repo become a graveyard of stale branches. But how do you even know what branches are there? Let me introduce you to git branches.
-
How to use .git/safe to trust the bin/ directory in your git repo.
-
There are pearls to be found. Check out these git logs.
-
GitHub’s squash and merge button is great. But make sure to write a good commit message before you confirm those changes.