Reduce the pre-commit autoupdate frequency to monthly #147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's kind of annoying to deal with weekly updates because we always have to revert the changes to the ruff hook, at least as long as we want to keep supporting Python 3.6. So I'm changing it to monthly. We could decide to further reduce the frequency or drop usage of pre-commit.ci entirely in the future. Closes #109
sjlongland
approved these changes
Jan 15, 2024
|
Sounds sane to me, we don't need to be on the bleeding edge. :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It's kind of annoying to deal with weekly updates because we always have to revert the changes to the ruff hook, at least as long as we want to keep supporting Python 3.6. So I'm changing it to monthly. We could decide to further reduce the frequency or drop usage of pre-commit.ci entirely in the future.
Closes #109
I'd probably recommend merging this after #138, but I'm not sure if it matters.