-
Notifications
You must be signed in to change notification settings - Fork 22.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci(cspell-bot): group words by file to reduce log size #38575
Conversation
831db93
to
2453173
Compare
Preview URLs External URLs (1)URL:
(comment last updated: 2025-03-14 12:37:45) |
Made some changes based on the review comments so far:
|
Successful run of the changes: https://github.com/OnkarRuikar/content/actions/runs/13805014898/job/38614067158#step:6:62 This is how the new issue looks: OnkarRuikar#46 |
|
||
```bash | ||
npx cspell --no-progress --gitignore --config .vscode/cspell.json "**/*.md" | ||
yarn lint:typos | ||
``` |
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.
Regarding the root cause of this problem, as far as I can see, anything generated from here conforms with our existing cSpell lorem-ipsum
dictionary: https://www.lipsum.com/feed/html
A good follow-up to this PR is:
- Update the container scroll-state queries page with passing Lorem text
- Mention this generator (https://www.lipsum.com/feed/html) in our writing guidelines somewhere as a hint for placeholder text.
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.
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.
I held back on submitting typo fixes so that when this PR merges, you'll manually trigger the workflow and we get to test these changes live.
Update the container scroll-state queries page with passing Lorem text
Agree. There is no point in having other versions of filler texts. We can also recommend the lorem-ipsum plugin in our https://github.com/mdn/content/blob/main/.vscode/extensions.json file. I will do the writing guidelines after these issues get resolved.
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.
- the writing guidelines have been updated here: fix(writing guidelines): Mention recommended sources for lorem ipsum #38677
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.
Thanks, Onkar! LGTM with a comment for when we're going to fix the typos afterwards
This pull request has merge conflicts that must be resolved before it can be merged. |
4650922
to
fb05222
Compare
This pull request has merge conflicts that must be resolved before it can be merged. |
fb05222
to
0c18a60
Compare
I think we're good to merge now, thanks 👍🏻 |
Problem
In the weekly spelling check bot, the current scheme of reporting each word on a separate line with corresponding file is generating massive logs. If someone adds a different version of lorem ipsum then it breaks the GitHub workflow with an error
https://github.com/mdn/content/actions/runs/13753835872/job/38458187038#step:5:876
Solution
Instead of having file-word combinations, have file-words combinations. That is, list a file path followed by the list of unknown words in it. It will reduce
files
xwords
lines to onlyfiles
.For example, the equivalent outcome of the failed workflow would be:
A custom CSpell reporter