fix typos #2519
fix typos #2519
Conversation
Originally detected/fixed in zenodo/zenodo#2519 Apparently there is 13k hits on github: https://github.com/search?q=verision&type=code The other possible close match is derision, which is a legit word and is used in about of 45k hits on github: https://github.com/search?q=derision&type=code 'd' is nearby 'v', so even though unlikely, I have decided that best to have multiple choices here.
|
What 's the explanation for the failing check?
The description fields originated externally to this repository and factually the modifications thereto should be reverted. |
|
it was incorrect to approve that the description fields be modified in that being said there neither appears to be forthcoming Maintainer response on this pull nor a decision on |
|
if "maintainer" is to be me -- please let me know what is desired to be done here??? Frankly I am surprised that this PR with such trivial fixes requires some more discussion and was not yet merged. |
|
The Author, Maintainer or Member may identify the relation of the individual to a ticket. |
Notwithstanding other Maintainer priorities, but I'm reluctant to even open a PR reverting those incorrect changes in |
|
must be me but I am not following. Anyways -- apparently I was assigned a reviewer, I approve . CI fails since python 2.7 is no more (so someone should address that separately). Let me know if I could be of any other help. |
|
@yarikoptic @musvaage I'm sorry to jump in this late. This repository has been somewhat inactive for the past year or so, because we've moved development over to https://github.com/zenodo/zenodo-rdm/ due to a large upgrade and migration to Zenodo. We plan to transfer the code back to this repository and continue development here, but there's no specific timeline for that. In the meantime, I will look into how it would be possible to notify/warn that PRs in this repository's current state should be avoided. Thank you for your contributions, but unfortunately I'll have to close this PR and #2470. |
|
@slint you can use |
Again, so it's not overlooked when development starts up again in this repo, those description fields were from external sources.
A reviewer to a GH pull would typically be a repo Collaborator, Maintainer or Member, that is someone with write authority. |
Originally detected/fixed in zenodo/zenodo#2519 Apparently there is 13k hits on github: https://github.com/search?q=verision&type=code The other possible close match is derision, which is a legit word and is used in about of 45k hits on github: https://github.com/search?q=derision&type=code 'd' is nearby 'v', so even though unlikely, I have decided that best to have multiple choices here.
Originally detected/fixed in zenodo/zenodo#2519 Apparently there is 13k hits on github: https://github.com/search?q=verision&type=code The other possible close match is derision, which is a legit word and is used in about of 45k hits on github: https://github.com/search?q=derision&type=code 'd' is nearby 'v', so even though unlikely, I have decided that best to have multiple choices here.
Originally detected/fixed in zenodo/zenodo#2519 Apparently there is 13k hits on github: https://github.com/search?q=verision&type=code The other possible close match is derision, which is a legit word and is used in about of 45k hits on github: https://github.com/search?q=derision&type=code 'd' is nearby 'v', so even though unlikely, I have decided that best to have multiple choices here.
cf: #2476 (comment)