Master Git’s Hidden Tricks: Reflog, Commit Fixes, and Branch Recovery

Git has become the most popular source‑code management tool thanks to its distributed nature, flexible branching, and easy deployment, but mastering it still requires significant learning effort. Many developers encounter confusing issues that generate thousands of questions on forums.

01 Reflog to Recover Lost Code

The git reflog command is extremely useful for retrieving accidentally deleted code, undoing bad merges, or rolling back to a previous version.

02 Fixing a Commit After Forgetting a Space

If you notice a formatting mistake (e.g., missing space before ‘=’) after committing, you can amend the change and combine commits using git rebase -i for a quicker fix.

03 Amending the Previous Commit Message

When a commit message needs correction or additional formatting, git commit --amend lets you edit the message without creating a new commit.

04 Accidentally Committed to Master

If you mistakenly commit changes to the master branch instead of a new branch, you can undo the commit with git reset HEAD@{number} (or git reset HEAD~ if executed immediately).

05 Diff Shows No Changes

git diff

only compares working‑tree files with the index; to see staged changes you must add the --staged flag.

06 Diff Produces No Output

Git will not diff files that are only added to the staging area unless --staged is specified; this is a feature, not a bug.

07 Git from Beginner to Giving Up

A humorous wrap‑up reminding readers that Git can be both powerful and frustrating, encouraging continued learning and sharing of tips.