You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While GitHub is an excellent place to centralize your code and keep it under version control, it is not so appropriate for archiving the state of the repository. Zenodo is a proper alternative, and it will even make your life easy by connecting to GitHub. I'd recommend following this tutorial to:
Create a "release" on GitHub, which automatically notifies Zenodo to make an archive
Go to the Zenodo page and grab the newly minted DOI which corresponds to the code as a resource
a. Put the badge on the GitHub page (it will allow you to copy+paste the markdown already prepared for you)
b. Put the DOI in your manuscript and mention that you're using Zenodo to do it.
I personally thing Zenodo is the best tool for code because of its integration with GitHub, but other services exist for archiving your research output that are also good, such as Figshare.
The text was updated successfully, but these errors were encountered:
While GitHub is an excellent place to centralize your code and keep it under version control, it is not so appropriate for archiving the state of the repository. Zenodo is a proper alternative, and it will even make your life easy by connecting to GitHub. I'd recommend following this tutorial to:
a. Put the badge on the GitHub page (it will allow you to copy+paste the markdown already prepared for you)
b. Put the DOI in your manuscript and mention that you're using Zenodo to do it.
I personally thing Zenodo is the best tool for code because of its integration with GitHub, but other services exist for archiving your research output that are also good, such as Figshare.
The text was updated successfully, but these errors were encountered: