Skip to content

Create README.md#1

Open
jsoref wants to merge 1 commit into
prereleasefrom
jsoref-patch-1
Open

Create README.md#1
jsoref wants to merge 1 commit into
prereleasefrom
jsoref-patch-1

Conversation

@jsoref

@jsoref jsoref commented Aug 1, 2024

Copy link
Copy Markdown
Member

No description provided.

Comment thread README.md
@@ -0,0 +1,5 @@
Teh quick brown foox jumps over the lazy dog.

Check failure

Code scanning / check-spelling

Unrecognized Spelling

[Teh](#security-tab) is not a recognized word. \(unrecognized-spelling\)
Comment thread README.md
@@ -0,0 +1,5 @@
Teh quick brown foox jumps over the lazy dog.

Check failure

Code scanning / check-spelling

Unrecognized Spelling

[foox](#security-tab) is not a recognized word. \(unrecognized-spelling\)
Comment thread README.md

When the wind blows, the cradle will rock.

Hoow many times times must things go this way?

Check failure

Code scanning / check-spelling

Unrecognized Spelling

[Hoow](#security-tab) is not a recognized word. \(unrecognized-spelling\)
Comment thread README.md

When the wind blows, the cradle will rock.

Hoow many times times must things go this way?

Check failure

Code scanning / check-spelling

Forbidden Pattern

[ times times ](#security-tab) matches a line_forbidden.patterns entry: "\\\s\([A-Z\]{3,}|[A-Z\][a-z\]{2,}|[a-z\]{3,}\)\\\s\\\g{-1}\\\s". \(forbidden-pattern\)
@github-actions

github-actions Bot commented Aug 1, 2024

Copy link
Copy Markdown

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

Unrecognized words (3)

foox
Hoow
Teh

To accept these unrecognized words as correct, you could run the following commands

... in a clone of the git@github.com:check-spelling/reimagined-chainsaw.git repository
on the jsoref-patch-1 branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/8b63ad52f62f9c28efb41d0ac54e24d794d33b05/apply.pl' |
perl - 'https://github.com/check-spelling/reimagined-chainsaw/actions/runs/10199117805/attempts/1'

OR

To have the bot accept them for you, comment in the PR quoting the following line:
@check-spelling-bot apply updates.

Forbidden patterns 🙅 (1)

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:

In English, duplicated words are generally mistakes

There are a few exceptions (e.g. "that that").
If the highlighted doubled word pair is in:

  • code, write a pattern to mask it.
  • prose, have someone read the English before you dismiss this error.
\s([A-Z]{3,}|[A-Z][a-z]{2,}|[a-z]{3,})\s\g{-1}\s
Errors (1)

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors Count
❌ forbidden-pattern 1

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 exclude README.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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants