Hacker News new | ask | show | jobs
by JetSetIlly 78 days ago
Some nice ideas but the regexes should include word boundaries. For example:

git log -i -E --grep="\b(fix|fixed|fixes|bug|broken)\b" --name-only --format='' | sort | uniq -c | sort -nr | head -20

I have a project with a large package named "debugger". The presence of "bug" within "debugger" causes the original command to go crazy.
4 comments
nozzlegear 78 days ago
This needs a small tweak to work on macOS, where git uses the POSIX version of grep (which doesn't support `\b`). You need to use the Perl Regexp option by switching -E with -P:

git log -i -P --grep="\b(fix|fixed|fixes|bug|broken)\b" --name-only --format='' | sort | uniq -c | gsort -nr | head -20

link
grepsedawk 77 days ago
Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.
link
j2kun 78 days ago
Similarly, we have a technical concept called "rollback" that is unrelated to a reverted commit.
link
grepsedawk 78 days ago
Good catch, that's better
link
Timwi 75 days ago
Word boundaries are one way to address that, but they require you to list all the inflections (and you missed “fixing”). Another way is to say (?<!de)bug.
link