Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMake it clear where config file should go #403
Closed
Conversation
It took me a while to work out where the file `.pre-commit-config.yaml` in step 2 should go. I think this small change will make it clearer for others.
|
the word "project" is ambiguous, I'd rather rely on the existing documentation thanks for the patch but I'm going to decline this |
| @@ -100,9 +100,9 @@ conda install -c conda-forge pre-commit | |||
| pre-commit --version | |||
| ``` | |||
| ### 2. Add a pre-commit configuration | |||
| ### 2. Add a pre-commit configuration to your project | |||
asottile
Oct 9, 2020
Member
I don't think this adds anything
I don't think this adds anything
| - create a file named `.pre-commit-config.yaml` | ||
| - create a file named `.pre-commit-config.yaml` in the root level of your project |
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.
It took me a while to work out where the file
.pre-commit-config.yamlin step 2 should go. I think this small change will make it clearer for others.