This repository has been archived by the owner on Jan 24, 2025. It is now read-only.
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.
Fix incorrect usage of the "[]" pattern format.
From Git documentation:
"[]" matches one character in a selected range.
Pull Request
Thank you for contributing to @dvcs/gitignore and https://www.gitignore.io.
New or update
Select the appropriate check box for this pull request. This helps when merging to ensure there are no conflicts with other templates or misunderstandings of how thee template list works.
New
.gitignore
templateUpdate
.gitignore
templateDetails
The previous usage of the range pattern ("[]") did not work as likely intended. From the Git documentation
Assumption was that the following rules were being condensed:
So:
acts as:
with duplicates removed, where only one character of the range pattern (
[]
) characters will be matched. The rest of the characters will be matched by the*
.This results in unintended matches (e.g.
coveragetype.sql
). The characterstype.sq
would be matched with*
and thel
would be matched by either form,[.json, .xml, .info]
or[.json, xmlif]
.