liveBook · Manning

Git log

As explained in Crack Any Codebase with AI

git log is a Git command that displays the commit history of a repository and can format or filter its output.

git log displays a repository’s commit history. Read it as an archaeological survey: filters choose which commits appear, while granularity controls how much each commit reveals. section 6.2

Find abandoned features

Run git log --diff-filter=D --name-only --pretty=format:"%at|%s" to surface deletion commits and the files removed. A large batch deletion can mark an abandoned feature or architectural reversal.

How Crack Any Codebase with AI covers it

How deep it goes
Distinguishes commit, file, and code granularity, then stops short of prescribing broader history analysis.
Examples
Demonstrates Ghost authentication middleware, deletion-filter output, commit receipts, and a crawler producing structured commit dictionaries.
What it assumes
Assumes familiarity with Git repositories and commits while teaching filters, granularity, and commit-history interpretation.
What you can do after
Diagnose architectural change by filtering commits, selecting an appropriate zoom level, and tracing features through files and code.
How it connects
Connects commits, files, code changes, filters, git show, and repository history.

Also explained in

Compare how 2 books explain git log →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Crack Any Codebase with AI. The section links point to the parts of the book it draws on.