Git, often perceived solely as a version control system, also functions as a sophisticated distributed database, enabling collaborative changes and historical investigations of repositories. This exploration reveals how Git's commit history can be queried in diverse ways, such as determining recent commits, identifying which tags or branches contain specific commits, and resolving merge bases. Git's unique structure, represented as a directed graph of commits, requires specialized storage and algorithms distinct from general-purpose graph databases, leading to the development of the commit-graph file which accelerates history queries by providing a structured index of commit data. The introduction of generation numbers, particularly corrected commit dates, enhances the efficiency of reachability queries by reducing the search space and preventing unnecessary walks through commit histories. These optimizations yield significant performance improvements in operations like tag containment, merge-base identification, and topological sorting of commits. As Git continues to evolve, its internal mechanisms become increasingly tailored to support large-scale repositories with complex histories, ensuring efficient data retrieval and manipulation.