4 posts tagged with "programming-tips"

That "Verified" badge on GitHub isn't just for show—it’s a cryptographic guarantee that the code actually came from you and hasn't been tampered with. Without it, anyone can technically spoof your name and email in a Git commit.

By using GPG (GNU Privacy Guard), you "seal" your commits with a private key that only you possess. GitHub then uses your public key to verify that seal.

This error usually pops up when you're trying to use the --author flag during a commit or a rebase, and Git is failing its "detective work."

Unlike a simple text label, the --author flag triggers a search. Git tries to find a match in your existing history or your configuration. If your search string is too vague, has a typo, or doesn't match the required pattern, Git throws its hands up and says: fatal: No existing author found with 'XYZ'.

Rewriting history in Git is a bit like time travel: it's powerful, but if you're not careful, you can create a messy alternate timeline. Since Git commits are cryptographically linked to their parent, changing an author changes the commit hash, which means you are technically replacing old commits with brand-new ones.

Finding the person behind a line of code is one of the most common tasks in Git—whether you're giving credit, asking for clarification, or (let’s be honest) finding out who broke the build.

In Git, every commit stores two distinct identities: the Author (who wrote the code) and the Committer (who put it into the repository). Usually, they are the same person, but they can differ during rebases or cherry-picks.