Início / coding / Perguntas / 79553244
Accepted
Sergey Zolotarev
Asked: 2025-04-03 22:33:03 +0800 CST

Pesquisa de texto em todas as revisões do Git

  • 772

Posso fazer git grepo cross all revisions em um repositório Git? Como?

Preciso procurar uma sequência de dígitos. Estou interessado no conteúdo dos arquivos, não apenas em mensagens de commit ou hashes. É aceitável limitar a busca somente a .javaarquivos, se isso ajudar.

Isso não funciona. O repositório é grande, pode ter algo a ver com isso.

git grep "509038" $(git rev-list --all)
Сбой выполнения программы git.exe: The filename or extension is too longстрока:1 знак:1
+ git grep "509038" $(git rev-list --all)
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
строка:1 знак:21
+ git grep "509038" $(git rev-list --all)
+                     ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Windows 10.

git

1 respostas

  1. Best Answer

    Você pode usar git log --all -S<some-text>para encontrar commits onde aquele pedaço de texto foi adicionado/removido no histórico. @LeGEC forneceu uma dica para usar -G<some-text>que, depois de ler como ela difere de -S, parece útil também.

    https://git-scm.com/docs/git-log#Documentation/git-log.txt-code-Sltstringgtcode

    -S<string>
Look for differences that change the number of occurrences of the specified <string> (i.e. addition/deletion) in a file. Intended for the scripter’s use.

It is useful when you’re looking for an exact block of code (like a struct), and want to know the history of that block since it first came into being: use the feature iteratively to feed the interesting block in the preimage back into -S, and keep going until you get the very first version of the block.

Binary files are searched as well.

-G<regex>
Look for differences whose patch text contains added/removed lines that match <regex>.

To illustrate the difference between -S<regex> --pickaxe-regex and -G<regex>, consider a commit with the following diff in the same file:

+    return frotz(nitfol, two->ptr, 1, 0);
...
-    hit = frotz(nitfol, mf2.ptr, 1, 0);
While git log -G"frotz\(nitfol" will show this commit, git log -S"frotz\(nitfol" --pickaxe-regex will not (because the number of occurrences of that string did not change).

Unless --text is supplied patches of binary files without a textconv filter will be ignored.

See the pickaxe entry in gitdiffcore[7] for more information.
    • 1

relate perguntas