-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pre-commit #103
pre-commit #103
Conversation
👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great @norlandrhagen, thanks for putting it together!
My only hesitation against merging now is that we've had a lot of bother in other repos with pre-commit autoupdate PRs. The problem is with prettier
, which has a series of 3.0.0-alpha.*
releases. We aren't interested in using pre-release versions of these tools, but the auto-update tool keeps trying to increment prettier to the latest alpha release.
So for months now we've been manually editing the auto-update PRs to strip away the prettier
update. It's been tedious, and I worry about spreading that tedium around to all the Cookbook repos...
I see three potential solutions:
- We just wait on merging this until prettier 3.0.0 is released
- We figure out a solution to prevent alpha releases from being included in the auto-update
- We change the frequency of auto-update. Currently it's weekly. If we reduced to monthly, that would ease the tedium quite a bit.
I don't know how to do 2 or 3! Any ideas?
Hey there @brian-rose, thanks for the feedback! I'm fine with any of those. Waiting until As for exploring option #2, I'm not sure if it works, but can we pin the - repo: https://github.com/pre-commit/mirrors-prettier
rev: v2.7.1
hooks:
- id: prettier
additional_dependencies: [prettier@v2.7.1] |
I don't know if it will work either, but let's give it a try! We can try it out here in the template repo for a week or so and see what autoupdates get generated. If we're happy these changes, then we can migrate them to all the existing cookbook repos. |
Thanks for your contribution @norlandrhagen ! |
Thanks @brian-rose! Not sure if it'll work, but fingers crossed. |
cc @brian-rose