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 is broken when installing #9459
Comments
Can you try - repo: https://github.com/prettier/pre-commit
rev: 2.1.2
hooks:
- id: prettier
exclude_types: [json] |
This works, thank you very much !!
|
We are migrating the pre-commit support to seperate repo. |
But should that migration break preexisting configurations? We had our version pinned and it was broken too... Did you move the git tag or something like that? 🤔 |
Related to prettier/prettier#9459 Signed-off-by: Matej Focko <mfocko@redhat.com>
Could you please roll back whatever change broke all prettier pre-commit configurations and provide a smoother migration path please? All our tests went red everywhere, not nice... 😿 🙏 |
We didn't do anything, my guess is some npm deps just broken. With this repo https://github.com/prettier/pre-commit, you'll get bundled Prettier, it's more stable. |
Looks like the format of the tags changed, so it now also needs to be "v2.1.2" instead of "2.1.2" etc. It's a shame this broke existing pipelines somehow. Now all will have to be changed to the new repo. |
Yes, although I am still facing an issue with plugins, that might be related to this: prettier/pre-commit#16 |
Yeah, you need change both the tag and repo. |
Yes. I misread, sorry. |
I'll sorry for the tag changes, didn't notice the difference between these two repos. |
See prettier/prettier#9459 for details. Unclear whether this is a prettier bug or an npm bug, but pre-commit fails with new repositories without this change.
See prettier/prettier#9459 for details. Unclear whether this is a prettier bug or an npm bug, but pre-commit fails with new repositories without this change.
Recently prettier got broken badly (see prettier/prettier#9459 and all the related PRs/issues there). This explains how to avoid that problem when updating templates.
Recently prettier got broken badly (see prettier/prettier#9459 and all the related PRs/issues there). This explains how to avoid that problem when updating templates.
If the cached pre-commit is deleted, pre-commit fails to install prettier/prettier#9459
If the cached pre-commit is deleted, pre-commit fails to install prettier/prettier#9459
If the cached pre-commit is deleted, pre-commit fails to install prettier/prettier#9459
If the cached pre-commit is deleted, pre-commit fails to install prettier/prettier#9459
If the cached pre-commit is deleted, pre-commit fails to install prettier/prettier#9459
@fisker - I see https://github.com/prettier/pre-commit mentions that it's been moved to https://github.com/pre-commit/mirrors-prettier so should we be updating the fix to point to that new one or is the prettier/pre-commit one still good to use? |
Use the new one please. |
Please refer to: prettier/prettier#9459
This fixes Prettier install failures similar to those seen in prettier/prettier#9459, and is the solution recommended there. Signed-off-by: Paul "TBBle" Hampson <Paul.Hampson@Pobox.com>
Environments:
Steps to reproduce:
Expected behavior:
Actual behavior:
The text was updated successfully, but these errors were encountered: