---
title: "TIL: git log Pickaxe Finds Who Deleted a Line"
description: The git log pickaxe, git log -S, lists only the commits that added or removed a piece of text. Use it to find when a line of code went missing.
canonical: https://lukeocodes.dev/til-git-log-pickaxe
type: article
locale: en_GB
published: 2026-10-27T00:00:00.000Z
modified: 2026-10-27T00:00:00.000Z
authors:
  - Luke Oliff
section: TIL
tags:
  - TIL
  - Git
  - git log
  - git history
  - debugging
  - cli
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/til-git-log-pickaxe#article
        headline: "TIL: git log Pickaxe Finds Who Deleted a Line"
        alternativeHeadline: "TIL: The git log Pickaxe Finds the Commit That Deleted a Line"
        description: The git log pickaxe, git log -S, lists only the commits that added or removed a piece of text. Use it to find when a line of code went missing.
        datePublished: 2026-10-27T00:00:00.000Z
        dateModified: 2026-10-27T00:00:00.000Z
        url: https://lukeocodes.dev/til-git-log-pickaxe
        mainEntityOfPage: https://lukeocodes.dev/til-git-log-pickaxe
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: TIL, Git, git log, git history, debugging, cli
        articleSection: TIL
        abstract: The git log pickaxe is git log -S "some text". It lists only the commits that changed how many times that text appears, so you get the commit that added it and the one that deleted it. git log -G also catches commits that edited a line with the text in it.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=TIL%3A+git+log+Pickaxe+Finds+Who+Deleted+a+Line&d=The+git+log+pickaxe%2C+git+log+-S%2C+lists+only+the+commits+that+added+or+removed+a+piece+of+text.+Use+it+to+find+when+a+line+of+code+went+missing.&e=Writing
        wordCount: 214
        timeRequired: PT2M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: "TIL: git log Pickaxe Finds Who Deleted a Line"
            item: https://lukeocodes.dev/til-git-log-pickaxe
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# TIL: The git log Pickaxe Finds the Commit That Deleted a Line

Oct 2026 · [TIL](/blog/category/til) · 2 min read · [Luke Oliff](/authors/luke)

**TL;DR:** The git log pickaxe is git log -S "some text". It lists only the commits that changed how many times that text appears, so you get the commit that added it and the one that deleted it. git log -G also catches commits that edited a line with the text in it.

`git log -S` finds the commit that added or deleted a piece of text. Git calls it the pickaxe, and the git log pickaxe is the quickest way I know to answer "which commit took this function out?"

```bash
git log -S "retryRequest" --oneline
```

Git keeps only the commits that changed how many times `retryRequest` shows up, so you get the one that added it and the one that deleted it. Add `-p` to see each change.

[git bisect](https://lukeocodes.dev/til-git-bisect-find-breaking-commit) tests commits one at a time to find what broke. If you already know the text, you do not need to test anything.

## When the git log pickaxe skips a commit

Changing `retries = 3` to `retries = 5` doesn't change how many times `retries` appears, so `-S retries` leaves that commit out. Use `-G` for those:

```bash
git log -G "retries" --oneline
```

`-G` takes a regex (a search pattern) and keeps any commit where an added or removed line matches it, so edits show up.

## Can I search one file?

Yes. Put the path after two dashes, like `git log -S "retryRequest" -- src/http.ts`. Git then only looks at changes to that one file. On a repo with years of history, that makes the git log pickaxe a lot faster.

[← Newer: What I Expect From a Workplace](/what-i-expect-from-a-workplace)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
