A Double Charge, Traced to Its Commit in Five Minutes

Filter a huge history down to the one commit that matters

One morning a report came in: since last week, some users were getting charged twice. The codebase was huge, with hundreds of files just around payments, and nothing was throwing an error. There was no obvious place to even start looking.

So before opening a single file, I asked the history. Running git log -S "chargeUser" on the payment function returned exactly one commit where that call had changed. Following up with git log --author and the commit message told the whole story: a retry added the previous week for flaky networks was firing the charge twice. When, who, and why, all at once.

Rather than grepping a massive codebase blindly, narrowing by -S (a code change), -- file (a file), and --author (a person) is dramatically faster. History is not just for reading; it is for questioning. Once you know when, who, and why a change went in, the fix usually reveals itself.