-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Fix typos in messages under aten #88964
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/88964
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 899e20d: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
These PRs are nice, but I believe that, at some point, we should have some sort of grammatical linter around...
@pytorchbot merge -f "grammatical changes" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
The question is which part should we apply grammatical linter to. |
There could be a PR that fixes all the grammar issues with comments and docs, followed by one that adds the relevant linter to the lintrunner. |
This PR fixes typos of messages and parms in c++ source files under `aten` directory. Pull Request resolved: pytorch#88964 Approved by: https://github.com/lezcano
This PR fixes typos of messages and parms in c++ source files under
aten
directory.cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @VitalyFedyunin @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10