document how to use ignore file types in configuration #22
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
|
👍 |
|
Thanks, I agree. |
hobbestigrou
added a commit
that referenced
this pull request
Oct 21, 2014
document how to use ignore file types in configuration
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.
I think that ideally the command-line parameter and the config file parameter for the type of ignore file to create should be the same, or at least there should be some spelling that's accepted for both, but perhaps there's a reason I haven't seen for this not being the case.
This commit just changes the documentation for the command-line tool to mention the difference and include an example of how to specify an ignore file type in the configuration, and thereby fixes issue #17 (which I found when googling for the problem I had). If you'd rather I fix it by changing the code to accept one or both of the spellings in both places, I'll do that instead.