I was trying to search through git logs to get a specific change that happened sometime in February to a specific file. I don’t remember how to format git logs off the top of my head so I reached for
grep. Unfortunately, I then remembered that the default
grep only returns 1 line per match. I finally had to break down and figure out how to get a context for my
What I found was that there is a
-C [number] flag you can pass to your
grep which will give you the number of lines above and below your match.
Here’s what I ended up with.
git log -- package.json | grep Feb -C 3
If you leave off the number after
-C it defaults to 2 (or at least on my MacBook Pro it does).
May the 4th be with you! Or happy Star Wars day. Whichever you prefer.