Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds options to
getGitCommitDateFromPath
which allows fine-grained filtering to select commits which (presumably) update content. This enables programmers who haveOCDset patterns and are stringent with commit messages to select more appropriate "last modified" dates.Example
Suppose I commit content-changes with the pattern
feat: updated post
. I can filter commits usingSuppose I use these other patterns:
chore: updated css
,bugfix: fixed logic
. I can exclude these commits using:These features might be a bit niche, but I thought it'd be a nice addition to this repo, in case others were looking for something similar.
Notes
--follow
to follow renames. If no options are provided, roughly the same speed.--grep
option, since it is buggy in conjunction with--follow
. The workaround implemented is to grab all commits (no-1
flag) and manually filter with JS.