-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(npm): bump stylelint-config-standard-scss from 13.1.0 to 14.0.0 (#…
- Loading branch information
1 parent
fb36781
commit c6e824a
Showing
2 changed files
with
62 additions
and
28 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"devDependencies": { | ||
"stylelint-config-standard-scss": "^13.1.0" | ||
"stylelint-config-standard-scss": "^14.0.0" | ||
}, | ||
"packageManager": "pnpm@9.1.4+sha512.9df9cf27c91715646c7d675d1c9c8e41f6fce88246f1318c1aa6a1ed1aeb3c4f032fcdf4ba63cc69c4fe6d634279176b5358727d8f2cc1e65b65f43ce2f8bfb0" | ||
} |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
c6e824a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@check-spelling-bot Report
🔴 Please review
See the 📜action log or 📝 job summary for details.
Unrecognized words (2127)
Some files were automatically ignored 🙈
These sample patterns would exclude them:
You should consider excluding directory paths (e.g.
(?:^|/)vendor/
), filenames (e.g.(?:^|/)yarn\.lock$
), or file extensions (e.g.\.gz$
)You should consider adding them to:
File matching is via Perl regular expressions.
To check these files, more of their words need to be in the dictionary than not. You can use
patterns.txt
to exclude portions, add items to the dictionary (e.g. by adding them toallow.txt
), or fix typos.To accept these unrecognized words as correct and update file exclusions, you could run the following commands
... in a clone of the git@github.com:jmuelbert/jmbde-QT.git repository
on the
main
branch (ℹ️ how do I use this?):Available 📚 dictionaries could cover words not in the 📘 dictionary
Consider adding them (in
.github/workflows/spelling.yml
) injobs:
/spelling:
foruses: check-spelling/check-spelling@67debf50669c7fc76fc8f5d7f996384535a72b77
in itswith
:To stop checking additional dictionaries, add (in
.github/workflows/spelling.yml
) foruses: check-spelling/check-spelling@67debf50669c7fc76fc8f5d7f996384535a72b77
in itswith
:Forbidden patterns 🙅 (4)
In order to address this, you could change the content to not match the forbidden patterns (comments before forbidden patterns may help explain why they're forbidden), add patterns for acceptable instances, or adjust the forbidden patterns themselves.
These forbidden patterns matched content:
s.b. macOS or Mac OS X or ...
s.b. GitHub
In English, it is generally wrong to have the same word twice in a row without punctuation.
Duplicated words are generally mistakes.
There are a few exceptions where it is acceptable (e.g. "that that").
If the highlighted doubled word pair is in a code snippet, you can write a pattern to mask it.
If the highlighted doubled word pair is in prose, have someone read the English before you dismiss this error.
s.b. anymore
Pattern suggestions ✂️ (37)
You could add these patterns to
.github/actions/spelling/patterns.txt
:Errors (7)
See the 📜action log or 📝 job summary for details.
See ❌ Event descriptions for more information.
If the flagged items are 🤯 false positives
If items relate to a ...
binary file (or some other file you wouldn't want to check at all).
Please add a file path to the
excludes.txt
file matching the containing file.File paths are Perl 5 Regular Expressions - you can
test yours before committing to verify it will match
your files.
^
refers to the file's path from the root of the repository, so^README\.md$
would excludeREADME.md (on whichever branch you're using).
well-formed pattern.
If you can write a
pattern
that would match it, try adding it to the
patterns.txt
file.Patterns are Perl 5 Regular Expressions - you can
test yours before committing to verify it will match
your lines.
Note that patterns can't match multiline strings.
🚂 If you're seeing this message and your PR is from a branch that doesn't have
check-spelling, please merge to your PR's base branch to get the version configured for your
repository.