Ignore commits starting with "META" in commit message #88
Conversation
|
re: incompatible with #86 and #87 Basically: we are in a holding pattern until that time. re: feedback on this PR
|
|
Thanks for feedback @klandergren. I'm glad this approach is compatible. Your suggestions are sound, but my Ruby skills are not strong. (In actuality, those skills barely exist beyond my ability to analyze, copy, and paste from StackOverflow.) If the project maintainer decides to pick up this PR and your PRs, I'll work on those suggestions. Otherwise, I'll just leave this here for others to know about. |
For reasons I couldn't determine, adding --follow to `git log` did
incompatable things with `--grep` ... the git command returned NO
entries. In other words:
git log --follow --grep "^META" --invert-grep -- {file}
...didn't work.
|
👋 Unfortunately, my GitHub notifications for this repository was oddly turned off. I take my responsibility to accepting patches seriously; however, I am just one person, with a very busy life off of GitHub.com! I'm going to close this PR because I like to keep my TODO list scoped and reasonable. This does not mean I will not accept this patch! Rather, it's a way of me asking you if you're still using this gem, and whether you want this PR merged. Just comment back and I'll prioritize it. I assume silence means I can keep it closed. Thanks! this was an automated copy-paste |
|
Hello! Would love to have this considered for inclusion in the main code. I'm still using it. |
For my blog, I want to ignore changes to the Jekyll front matter—changing tags and the like. This commit adds
--grep=^META --invert-grepto the Gitlogcommand. Any commit messages starting with "META" are ignored for the purposes of displaying the last-modified date.I'm unsure if the caching proposals in #86 and #87 by @klandergren are incompatible with this change or if @trickv's option of AuthorDate (#53) is a better approach.