Trace a line range through Git history
Line history starts from a particular revision and follows the selected range, so choose that starting point deliberately.
Topic · 25 stories · page 1 of 2
25 stories tagged git on AI Tamer, newest first.
Line history starts from a particular revision and follows the selected range, so choose that starting point deliberately.
Pickaxe occurrence counts and matching changed lines find different kinds of edits.
Git can flag whitespace problems, but the comparison you select determines which changes it sees.
OpenAI is acquiring Pierre Computer Company, maker of Code Storage and the Trees and Diffs libraries already in the Codex app. The deal still needs approvals.
OpenAI says Pando, built in Rust with Codex in 10 weeks, cut median push latency by nearly 80%. It runs only inside OpenAI; you can't use it yet.
When a branch was built on another feature branch, the three-argument git rebase --onto moves just its own commits onto main.
What the Content-Digest header actually protects against, and why a digest is not proof of origin without TLS or a signature.
A bare --force-with-lease checks your remote-tracking branch, which a background fetch of that remote can move. Add --force-if-includes or name the expected commit.
Thomas Dohmke's Entire launches a Git-compatible forge with Trails, review agents, merge Gates, GitHub mirroring and two MIT-licensed memory CLI plugins.
GitHub may require sign-in for some anonymous HTTPS clones and fetches of public repos during unusual traffic. SSH, pushes and authenticated Git still work.
Anthropic says daily merges rose from around 2,500 in May to over 30,000 in September, and that seven people built Scion in five months.
An architecture decision record is a short file in your repository that explains one design choice: its context, the decision, its status and its consequences.
A shallow CI checkout can build the current tree while hiding the ancestor a change detector needs. Diagnose missing history, deepen deliberately, and fetch the right refs.
The local Qwen engine Strata force-replaced all 845 commits on main on 6 October. File trees match, but Claude Code co-author trailers are gone. The maintainer shipped a migration fix and has not said why.
A displaced Git commit may still be in your local reflog. Here is how to find it, inspect it, and give it a branch before the recovery window closes.
A sparse checkout can leave tracked files out of your working directory. Check Git's index and the current commit before treating an absent file as a deletion.
Linked worktrees give parallel coding tasks separate branch checkouts in one Git repository. Here is how to create, inspect, and retire them safely.
When a conflict returns during a rebase, Git can reuse the resolution you made earlier. You still need to inspect the result before continuing.
Attach review context to an existing commit while leaving the commit object unchanged. Share the notes ref when collaborators need to see it.
Commit graphs speed up history walks. Incremental repacking keeps object lookup manageable as pack files accumulate.
A committed .gitattributes file can keep tracked patch files on consistent line endings across operating systems. Here is how to set and check the rules.
Turn a repeatable refactor failure into a search across commits. Use Git to narrow the range, then inspect the first failing change.
Cloudflare's 1 October 2026 posts put Artifacts, its Git-speaking versioned filesystem, in open beta. A contest for agent-era Git tools closes 14 October, and usage billing starts 15 October.
A reviewer finds mistakes faster when a diff holds one change, shows moved code as moved, and comes with a clear description. Here is what Google's review guide and the git manual say about it.