new: added 'path' config option to limit commit messages #112
Conversation
…e affecting files under the give repo path
Codecov Report
@@ Coverage Diff @@
## master #112 +/- ##
=======================================
Coverage 88.45% 88.45%
=======================================
Files 2 2
Lines 840 840
Branches 168 168
=======================================
Hits 743 743
Misses 58 58
Partials 39 39
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Thanks for the tests... while reading your code, I was wondering if we should support a list of paths instead of only one.
Your code doesn't seem to support path containing white-spaces. A test for that would be welcome anyway.
Fixing this should not be trivial and is probably different between linux and windows.
I like the idea, and will be happy to accept the PR if the white-spaces issue is fixed (with a test).
| % (GIT_FULL_FORMAT_STRING, | ||
| '--no-merges' if not include_merge else ''), | ||
| '--no-merges' if not include_merge else '', | ||
| '--' if not path else '-- ' + path), |
There was a problem hiding this comment.
Why not keep "-- %s" in the main string ? And something like path or "" ?
This introduces a new optional 'path' config file parameter which allows end-users to run 'git log ... [path]' instead of 'git log ...'. The net effect here is this makes it easy to limit commits to those that affected a certain set directory and its contents only. Hopefully this capability didn't already exist in some other capacity:)