Как раз то, что я искала! Думаю, что за grep такой)) Thanks!

and nowdays, helix

> _"pickaxe" which is searching among patches for an occurrence of a string"_ > _"when a piece of code (like a function call) was added or even removed"_ i was also thinking about the ability to search within diffs/patches only

Interesting, I wasn't aware there was such guidance on tense of the commit messages. Good suggestion for a new video, I'll have to get smarter about the style conventions first. Thanks for watching!

You have to comply with the guidelines for commit messages the git developers like when contributing to git. Those seem to be pretty much the same rules you find when googling for commit message guidelines. I don't agree with all of them. That's why I think hearing the opinion of someone else who knows a lot about git would be interesting. Whether you write in simple past or imperative is a matter of taste, imho. But there are stupid rules like using at most 50 characters in the first line but leaving out the period in the end to save one character because staying below 50 characters can be difficult. I think leaving out the period in the end of a sentence is just pointless (no pun intended) when only trying to comply to an arbitrary limit which can just be increased by 1 to make up for the 1 character "wasted" for proper punctuation. Another imho stupid one it to do hard line breaking. I think doing proper visual line wrapping in the few cases the commit messages are printed isn't really difficult and it has two advantages: 1. You can view them in a terminal of arbitrary width. If the terminal you use is wider than the line wrapping length of hard line breaking, space is wasted. If it's smaller, it looks really, really awful. 2. If you edit a commit message after first writing it, undoing hard line breaking is wasted time. No need to do this with visual line wrapping. The git developers could just implement visual line wrapping, remove that rule, and be rid of the disadvantages of hard line breaking outlined above. I don't really see any disadvantages.

Not sure what you mean. If you are asking if you can git grep over submodules, you can embed the command in a 'git submodule foreach 'git grep... ' ' to grep across any submodules as in the project. But no you can't git grep "outside" a particular repo because there's no history outside a repo!

Dan Gitschooldude yeah I meant my company has over 100 repos and sometimes we need to search code across all of them

Ah, I see. You'll probably want to write a script that traverses all your repos and executes the 'git grep' command in all of them. If your repos are all in a tool like Gitlab, you might be able to search across multiple projects, but I'm not sure if that's a feature in Gitlab or not. Thanks for watching!

Dan Gitschooldude I was also looking for the same thing as described by Roman in above comment.