Kubernetes Manifest Studio
Generate Deployment, Service, and Ingress YAML with a drift checklist.
OpenA compact git blame reference to keep open while you dig through history.
Learn what each part of a blame line tells you.
Use -L to blame only the lines you care about.
Add -w for whitespace and -C for moved or copied code.
Run git show on the hash to read the full change.
A strange condition in a payment handler looks like a bug, but before removing it you want to know who added it and what problem it solved. git blame answers that, as long as you know which flags cut through whitespace changes and moved code.
This page is a short, copyable reference rather than an interactive tool. It covers what each blame column means (commit, author, date, line number and code) and three flags that matter in practice: -L 10,40 to limit output to a range of lines, -w to ignore whitespace-only changes, and -C to follow code moved or copied from other files. It ends with the next step, running git show on the hash to see the full change and its message.
A common trap is that blame shows the last commit to touch a line, which is often a formatting or rename commit rather than the one that introduced the logic. Re-run with -w, or blame the parent of that commit (git blame HASH^ -- path) to step further back. Git can also skip bulk-formatting commits that you list in a file passed to --ignore-revs-file.
Nothing is processed here; the reference is static text. Once you find the commit, the log hash formatter tidies a list of related hashes for a ticket, and the git reset mode helper explains how to back out a recent local commit.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Blame the parent of that commit with git blame HASH^ -- path, or list formatting commits in a file and pass it with --ignore-revs-file so blame skips them.
No. It is a reference sheet. Run the commands in your own terminal; the page never reads your code.
-M detects lines moved within the same file. -C also looks for lines moved or copied from other files changed in the same commit, and repeating it widens the search further at the cost of speed.