-
Notifications
You must be signed in to change notification settings - Fork 9.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
minor typo #9033
minor typo #9033
Conversation
neg_pos_up -> neg_pos_ub minor typo fix
Hi @Ryoo72 Thanks for your kind PR. It seems that CLA is not signed. Could you sign the CLA so that eventually we could merge this PR after review? You can check the contents and follow the instruction in the communication box shown as below |
Codecov ReportBase: 64.12% // Head: 64.07% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## dev #9033 +/- ##
==========================================
- Coverage 64.12% 64.07% -0.06%
==========================================
Files 361 361
Lines 29536 29536
Branches 5022 4920 -102
==========================================
- Hits 18939 18924 -15
- Misses 9580 9593 +13
- Partials 1017 1019 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
I really appreciate your detailed explanation ! Thank you :) |
neg_pos_up -> neg_pos_ub minor typo fix
neg_pos_up -> neg_pos_ub
minor typo fix
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Debugging today was difficult because searching with ctrl+shift+f was not possible due to a typo.
Modification
I just changed one letter. neg_pos_up -> neg_pos_ub
I just want to fix this typo, and I was thinking about whether to drop it in an issue or make a pull request and post it here. If you've read this, I'd appreciate it if you could correct the typo. thx !
Checklist