Add wildcard search to commit messages

18 votes

In our commit messages we put url's to the tasks the commit is linked to, i.e. https://tasklister.somesite.nl/task?123456

When searching the commit messages list (with ctrl+F) for the task number 123456, the commit is not found. We resolve this now by also adding "task 123456" to the commit message.
Having a wildcard search option like *123456 should then find the commit. That would be a great help.

Under consideration Suggested by: Roland (21 Sep, '21) • Upvoted: 28 Mar • Comments: 5

Comments: 5

29 Sep, '21
Vladislav Javadov
Even regexps. 🙄
13 Oct, '21
Matthew Chestnut
We also could use this feature. We are using scoped commit messages, but currently there is no way to search by the scope since it is formatted within parenthesis.

** Example commit messages **
build(utilities.purchasing): build package on precommit
feat(utilities.purchasing): add props and methods to fee module
chore(sample-vue): remove extra props from package.json

** Current result **
Performing a search for "utilities.purchasing" returns no results

** Desired result **
Performing a search for "utilities.purchasing" would return the first commits but not the third
26 Jan, '22
lingtalfi
In addition to the wildcard suggestion, I say when you type 123456 it only makes sense that by default it founds any commit that contains that string in it, in other words that the string you type searches in the whole commit message.

I say that because I also need this feature. This feature is why I moved from SourceTree in the first place, I needed a tool that could find commit by typing a string.
22 Mar, '22
The-Dung Nguyen
Agreed with lingtalfi, most systems use the 'searchString' as "Contains" behavior. My current workaround is to have a Gitkraken console open:

git log --all --grep='searchString'
13 Feb, '23
GM
It's ironic that the left panel filtering (branches, etc) is way too fuzzy.

However, I can't search commit messages with a plain branch name for it to match local and remote branches.