-
Notifications
You must be signed in to change notification settings - Fork 88
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
[FEATURE] Use repo prettier configuration. #41
Comments
That would be a good idea! We don't have this in place yet, I always do it via the |
@creyD I don't want to hijack this request but I'm having a similar question regarding the use of the Error: No parser could be inferred for file: x/y/assets/[email protected]
Error: No parser could be inferred for file: x/y/assets/[email protected]
Error: No parser could be inferred for file: x/y/assets/[email protected]
Error: No parser could be inferred for file: x/y/assets/[email protected] My prettierignore looks like this:
Workflow yaml: - name: Check Code Formatting
uses: creyD/[email protected]
with:
# only_changed: true
dry: true
prettier_options: --write x/y/**/* --ignore-path "./.prettierignore" As a workaround, I'll just add the filetypes to the |
Oh, you are ignoring the .prettierignore file, that's why you are getting some problems about unknown file formats. remove the ignore-path flag and you're good to go. |
I'm having a similar issue where it seems like this action isn't respecting my |
@johannbotha I suppose |
Taking this a step further, would it be possible to use the repo's installed version of prettier? Its easy for the |
I'v actually test it and it does. |
What would you like to change about the program?
I would like to be able to use the repo prettier configuration, instead of putting it into the action configuration, if it is already possible, how can I do it?
Why do you think this is a cool idea?
Automate more the usage of this action.
The text was updated successfully, but these errors were encountered: