-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
chore: fix spelling errors in multiple files #34574
Conversation
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 vast majority of fixes were suggested by Google Sheets.
All fault is mine.
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.
Hey @jsoref, thanks for opening a PR here! I appreciate the PR with corrections, and also think the tool you're developing is very cool - but the format of the PR right now is a bit tough to review as a maintainer. Would you mind making the following changes? I'd be happy to review it after that:
Commits: We squash merge, so having multiple commits is fine here, but having a commit for each change makes it a lot harder to review individual changes. Would it be possible to rebase/squash these so that each commit contains all of the changes in a given directory (e.g. "docs", "script", "build", etc)? That would also let us identify more easily which typo changes could actually cause breaks - "docs" is unlikely to break anything, "build" more so. I'm also open to another way of organizing them if you'd like - but the goal is fewer, more clear commits.
PR Title: The title of the PR will be the text of your squashed commit - right now, that title isn't very descriptive. Could you change the title to be slightly more descriptive (appreciate the semantic commit at the beginning)
Once those two changes are made, I'll give this a proper review. Thanks for your time!
@VerteDinde: happy to squash. I generally prefer to squash at the end as it makes it easier and safer for me to drop individual corrections if they are deemed objectionable. The problematic commit if I squash by directories is: I'll just fold it in w/ that directory. I'm happy to reword the PR title, although I don't have any particular ideas (I'm not particularly creative). Anyway, squashed incoming... |
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
bool new_invertered_color_scheme = IsInvertedColorScheme(); | ||
if (new_invertered_color_scheme != invertered_color_scheme_) { | ||
invertered_color_scheme_ = new_invertered_color_scheme; | ||
Emit("inverted-color-scheme-changed", new_invertered_color_scheme); | ||
bool new_inverted_color_scheme = IsInvertedColorScheme(); | ||
if (new_inverted_color_scheme != inverted_color_scheme_) { | ||
inverted_color_scheme_ = new_inverted_color_scheme; | ||
Emit("inverted-color-scheme-changed", new_inverted_color_scheme); |
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.
Just a note for future PRs: I'm generally fine with typo fixes in PRs when they deal with comments, docs, and tests.
Changing actual variables in code as part of a larger typo-fixing PR - when the rest of the PR doesn't directly deal with the corresponding code or explicitly fixing a bug - is riskier, and I'd really like to avoid doing that. These specific changes seem small and don't negatively impact the rest of the code, so I'm fine merging them with this PR, but this would likely be a merge blocker from me in the future.
Congrats on merging your first pull request! 🎉🎉🎉 |
No Release Notes |
* chore: fix spelling in .circleci Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in BUILD.gn Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in appveyor.yml Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in build Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in docs Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in lib Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in script Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in shell Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec-main Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Description of Change
Fixes various typos in electron
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at jsoref@da81883#commitcomment-76118321
The action reports that the changes in this PR would make it happy: jsoref@39e7178
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
I will be annotating this PR, and I fully expect to be asked to drop certain files.
Checklist
npm test
passesRelease Notes
Notes: none