-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Infra spell bot #35224
Infra spell bot #35224
Conversation
Preview URLs
External URLs (1)URL:
(comment last updated: 2024-08-13 07:12:42) |
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.
For the corrections to favourite-colour
- name: Create an issue | ||
if: env.OUTPUT != '' | ||
uses: dacbd/create-issue-action@main | ||
with: | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
title: Weekly spelling check | ||
body: | | ||
## Found typos and unknown words: | ||
${{ env.OUTPUT }} | ||
|
||
> [!TIP] | ||
> Add valid words to the https://github.com/mdn/content/blob/main/.vscode/project-words.txt file, and fix the 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.
Instead of creating one issue every week, is it possible to keep one dashboard issue that gets updated every week? No strong feelings, just because our issues tend to stack up and get forgotten—not everyone here has the habit of going through past issues.
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 hope the typo issues will not linger more than a day. A maintainer won't even have to wait for a reviewer.
There are many things to handle. We'll have to reopen the issue every week and update it. We might need a custom implementation for this. If you know of any third-party action that does this out of the box, let me know.
How about we merge this as it is and get this bot going, then work on the recurring issue implementation?
@OnkarRuikar Perhaps you can split out the content change into a separate PR so it can be quickly merged? #35404 |
@OnkarRuikar Could you split all content changes into separate PRs? We don't want to loop more and more people into this. |
cc99af8
to
33dda95
Compare
I see that they won't be added to editor suggestions. However I think in |
Because the bot was working standalone and the editor consideration was not there so all the words were accumulated in one file. There are 5578 words in the file, and classifying them is a huge time-consuming task. But we can do it later after the bot goes live. If we could force contributors to use camel case variable names then a ton of words will get removed. 🙄 |
Co-authored-by: Brian Thomas Smith <brian@smith.berlin>
94c1034
to
40c444f
Compare
Co-authored-by: Brian Thomas Smith <brian@smith.berlin>
I've successfully tested the workflow. |
It looks good, tnx. I think we can merge this shortly. I would also echo the sentiment from Josh that we should try to reduce the 5k+ size dictionary by some means in a follow-up. Like:
|
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.
One last thing I noticed; we have dupes in the ignore-words.txt
file, could you uniq
it first?
edit: Also if you think renaming the dictionaries will help with their purpose, we can do that in this PR, for instance ignored-words
-> ignore-list
?
I ran |
nice, thank you
IMO "words" is the part to get rid of in the ignore file, so I'd prefer to keep the original or do something like:
What do you reckon? |
@bsmth |
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.
Looking good, let's give it a shot! Thanks, Onkar
Don't forget to trigger the workflow manually. |
I've been running a spell-checker bot in my
temp
repo for over 1.5 years. The bot runs every Monday start and files an issue giving details about found typos/spelling mistakes in themdn/content
repo. The issue is resolved by fixing typos inmdn/content
and adding new words in theproject-words.txt
file.In the last weekly meeting, we got the green signal to move the bot to the content repo. The PR moves the bot to this repo.
The following changes have been made to existing files:
project-words.txt
file contains 5k+ ignored words gathered over the period.valid=true
casefavourite-colour
. As the article is named in such a way, we have to ignore all the occurrences.