mirror/PowerToys
1
0
Fork 0
mirror of https://github.com/microsoft/PowerToys.git synced 2024-12-12 10:19:20 +08:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
43a73065af
PowerToys/.github/actions/spell-check/patterns.txt

64 lines
1.5 KiB
Plaintext
Raw Normal View History

Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
# See https://github.com/check-spelling/check-spelling/wiki/Configuration-Examples:-patterns
Set up spell-checking action
2020-05-21 11:19:08 +08:00
https?://(?:(?:www\.|)youtube\.com|youtu.be)/[-a-zA-Z0-9?&=]*
Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
# GitHub SHAs
\bapi.github\.com/repos/[^/]+/[^/]+/[^/]+/[0-9a-f]+\b
Set up spell-checking action
2020-05-21 11:19:08 +08:00
://github\.(?:com|blog)/[^\w")]+
Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
(?:\[[0-9a-f]+\]\(https:/|)/github\.com/[^/]+/[^/]+/[^/]+/[0-9a-f]+(?:[-0-9a-zA-Z/#.]*|)\b
# githubusercontent
Set up spell-checking action
2020-05-21 11:19:08 +08:00
://githubusercontent\.com/[^\w")]+
Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
# gist github
/gist\.github\.com/[^/]+/[0-9a-f]+
# msdn
\b(?:download\.visualstudio|docs|msdn)\.microsoft\.com/[-_a-zA-Z0-9()=./]*
Set up spell-checking action
2020-05-21 11:19:08 +08:00
data:[a-zA-Z=;,/0-9+-]+
0x[0-9a-fA-F](?:\.[0-9a-fA-F]*|)[pP]
(?:0[Xx]|U\+|#)[a-f0-9A-FGgRr]{2,}[Uu]?[Ll]{0,2}\b
Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
# uuid:
[-<({"'>][0-9a-fA-F]{8}-(?:[0-9a-fA-F]{4}-){3}[0-9a-fA-F]{12}[<'"})>]
# ignore long runs of a single character:
\b([A-Za-z])\g{-1}{3,}\b
Set up spell-checking action
2020-05-21 11:19:08 +08:00
(?:L"[abAB]+", ){3}L"[abAB]+"
"Lorem[^"]+?\."
TestCase\("[^"]+"
fix misspellings
2020-11-09 13:30:36 +08:00
# Test line with hexadecimal colors
\[DataRow\("[0-9A-F]{6}", \d{3}, \d{3}, \d{3}\)\]
fix spelling
2020-11-09 13:46:13 +08:00
\[DataRow\("[0-9A-F]{6}", \d{3}.\d{1}, \d{3}.\d{1}, \d{3}.\d{1}\)\]
Fix pattern
2020-11-09 16:33:57 +08:00
\[DataRow\("[0-9A-F]{6}", "[BCGMRY]\d\d?", \d{3}, \d{3}\)\]
fix misspellings
2020-11-09 13:30:36 +08:00
Set up spell-checking action
2020-05-21 11:19:08 +08:00
# Windows paths
\\native
\\notifications
\\recyclebin
\\reinstall
\\Resize
\\resource
\\Resources
\\restart
\\restore
\\result
\\runner
\\Telemetry
\\telemetry
\\testapp
\\tests
\\tools
[PT Run] Registry plugin (#7951)
2021-01-21 02:15:45 +08:00
# plugin.json
^ "ID": "[0-9A-F]{32}",$
# UnitTests
\[DataRow\(.*\)\]
# Id info inside markdown file (registry.md)
^\|\s+ID\s+\|\s*\`[0-9A-F]{32}\`
# marker for ignoring a comment to the end of the line
^.*/\* #no-spell-check-line \*/.*$
0.31 release notes (#9306) * Update README.md * Update expect.txt * Update README.md * adding EOF adding EOF * Update README.md * Update README.md * Update README.md * Update README.md * Update README.md * Apply suggestions from code review Co-authored-by: htcfreek <61519853+htcfreek@users.noreply.github.com> Co-authored-by: Deondre Davis <dedavis@microsoft.com> * Apply suggestions from code review Co-authored-by: htcfreek <61519853+htcfreek@users.noreply.github.com> * Update README.md * Update README.md Co-authored-by: htcfreek <61519853+htcfreek@users.noreply.github.com> Co-authored-by: Deondre Davis <dedavis@microsoft.com>
2021-02-03 01:40:01 +08:00
// #no-spell-check.*$
Upgrade check-spelling to 0.0.17-alpha (#10173) * spelling: snapped Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * spelling: split Signed-off-by: Josh Soref <jsoref@users.noreply.github.com> * ci: update to Spell check to 0.0.17a In the past, plurals `foo`+`s` and past tenses `foo`+`ed` were automatically tolerated. This turned out to be a bad design choice on my part. The basic example is that `potatos` would sometimes be treated as a mistake and sometimes not (depending on the presence of `potato`). You can see in this PR, that this logic resulted in `SNAPED` being accepted as a word along with `actioned` -- there's nothing intrinsically wrong w/ the latter, but unfortunately in order to screen out the former, my shortcut just couldn't stick around. This means that the `expect` files will grow perhaps by a tiny bit, but as you can see, not really by much. When GitHub initially introduced GitHub Actions, the event for `pull_request` was created without enough permission for a tool like this to work properly. I worked around that by using the `schedule` event. In 2020, they introduced a replacement event `pull_request_target` which has enough permission. This means that I can stop relying on the `schedule` event.
2021-03-18 02:27:30 +08:00
http://tes/
Reference in New Issue Copy Permalink