Do not treat trailing #
in gitignore as comment
#797
Merged
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.
Just started using
knip
today and it was instrumental in some really nice cleanup in our codebase. I hit #795 right off the bat, though, and it took me a while to figure out what was going on. I figured I could say "thanks" by opening up a quick PR to fix the issue!The logic in the gitignore parser that strips trailing
# ...
off of.gitignore
lines appears to be wrong. In my testing, you cannot add a comment to the end of a.gitignore
line in this manner (syntax highlighting be damned):This tracks with git's documentation (emphasis mine) as well as my own messing around with git:
The previous parsing logic (added in e455527) stripped all non-backslashed
#...
out. I updated the logic to only strip a leading\
, if it's in front of a hash, so the following cases will be handled properly: