Closed kalkin closed 5 years ago
This change would be much simpler if we instead check the time in which the cached results were generated and the last modification timestamp of the configuration file.
This change would be much simpler if we instead check the time in which the cached results were generated and the last modification timestamp of the configuration file.
Yes but then you would have to run all linters for the same file and not only the linter whose configuration changed. If you still prefer just to check the timestamp, i will adjust the commit.
Closing because I replaced git-lint with custom written software and author isn't interested in this PR.
When arguments in .gitlintrc change
git-lint
still serves the old cached results. This commit changes it.