-
Notifications
You must be signed in to change notification settings - Fork 84
add Zenodo integration issue template #256
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
Conversation
sverhoeven
left a comment
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.
Instructions work, tested it against Zenodo sandbox and Zenodo record was created.
The Next step: Citation data issue asks you to create a .zenodo.json file which could cause change in Zenodo record in next release. For example my Zenodo record title is sverhoeven/justatest: v0.1.0 instead of justatest.
Should we change the order and make Next step: Zenodo integration issue depend on Next step: Citation data issue?
The instructions uses the versioned DOI instead of the concept/latest DOI. Should we prefer the concept DOI?
{{cookiecutter.project_name}}/.github/next_steps/02_zenodo_integration.md
Outdated
Show resolved
Hide resolved
|
|
||
| 1. Go to http://zenodo.org and login with your GitHub account. When you are redirected to GitHub, *Authorize application* to give permission to Zenodo to access your account. | ||
| 1. Go to <https://zenodo.org/account/settings/github/> and enable Zenodo integration of your repository by clinking on `On` toggle button. | ||
| 1. Your package will get a DOI only after you make a release. Create a new release on <{{cookiecutter.repository}}/releases/new> |
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.
Can we point to README.dev.md#33-github instead of {{cookiecutter.repository}}/releases/new?
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.
Also link is broken as it renders as </releases/new>, but will be fixed in #261
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.
updated the link
Yes |
Yes |
…egration.md Co-authored-by: Stefan Verhoeven <stefan.verhoeven@gmail.com>
Thanks for suggesting this. I have changed the order. |
sverhoeven
left a comment
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.
Looking good. Just one major inline suggestion about concept DOI and some typo corrections.
{{cookiecutter.project_name}}/.github/next_steps/04_zenodo_integration.md
Outdated
Show resolved
Hide resolved
{{cookiecutter.project_name}}/.github/next_steps/04_zenodo_integration.md
Outdated
Show resolved
Hide resolved
{{cookiecutter.project_name}}/.github/next_steps/04_zenodo_integration.md
Outdated
Show resolved
Hide resolved
{{cookiecutter.project_name}}/.github/next_steps/04_zenodo_integration.md
Outdated
Show resolved
Hide resolved
…egration.md Co-authored-by: Stefan Verhoeven <stefan.verhoeven@gmail.com>
…egration.md Co-authored-by: Stefan Verhoeven <stefan.verhoeven@gmail.com>
…egration.md Co-authored-by: Stefan Verhoeven <stefan.verhoeven@gmail.com>
…egration.md Co-authored-by: Stefan Verhoeven <stefan.verhoeven@gmail.com>
sverhoeven
left a comment
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.
LGTM
Fixes #235
Important Note:
Please use https://sandbox.zenodo.org/ instead of https://www.zenodo.org/ to test the instructions otherwise entry you create on Zenodo cannot be removed easily.
Summary
This pull request adds an issue template for Zenodo integration.
Testing