-
Notifications
You must be signed in to change notification settings - Fork 245
chore: fix typos #2476
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 typos #2476
Conversation
Hi, please ignore and close, if this is obsolete because of #2470. But I guess codespell cannot find occurences of "the the" and other grammar related things, that are not dictionary lookups. |
to date neither PR has been commented on by repo Contributors/Maintainers the predecessor linked to PR ( CONTRIBUTING.rst - repository). Please include the the word ``SECURITY`` in all-caps in the email
+ repository). Please include the word ``SECURITY`` in all-caps in the email tests/unit/deposit/test_api_simpleflow.py - # Publish new verision
+ # Publish new version |
Do you approve fixing that typo?
I'd have approached the subject matter of
FWIW, the majority of the commits to this repo appear to be 2 to 8 years old. zenodo/modules/fixtures/data/records.json I don't see any reason to change the code of @lnielsen to read Of the root words automate, automatise/automatize, the former since the mid 1950s appears more prevalent.
Incidentally, the motive of @luzpaz in upvoting The user is a codespell [-project] Collaborator, with no history as a zenodo Contributor. |
cf: #2423 (Closed) Modifying description fields in records.json may seem innocuous. For 10.5281/zenodo.13113 however it is definitely on Abstract As C++11 gained almost full support by compilers, it is interesting to see whether we can leverage some of the features to improve performance and reliability of C++ code. This work is focused on four selected problems: time measurement techniques, for-loops efficiency, asychronuous tasks and parallel mode of STL algorithms. For each of them a micro-benchmark is made. All the benchmarks are fully At this point of time my preference would be to close I've asked @mitsosf about modifying test_schemas_legacyjson_load.py.
Would you furthermore approve these limited modifications to records.json?
pull If Whether OpenAire would have problems with the .json file changes is unknown.
Non-Intrusive User Interaction Monitoring for WinCC OA based Applications
Zenodo: Preservation Meter
Evaluating the Performance of Seagate Kinetic Drive Technology and its Integration into the
Evaluation of selected C++11 features with GCC, ICC and Clang @mitsosf, @ppanero In retrospect if any of the description fields modified in |
Closing this due to inactivity. Feel free to open a PR yourself @musvaage. |
|
Hi, this is my first PR to the project.
Should PRs be pointed at the master branch?
I propose to fix some minor typos (mostly in comments and docstrings).
I was unsure about typos in function, method or class names, e.g.
zenodo/tests/unit/records/test_schemas_legacyjson_load.py
Line 454 in 2dbd8ca
What do you think?