Zenodo: github: inclusion of release assets in published record

Created on 26 Jul 2017 · 5Comments · Source: zenodo/zenodo

It's common for GitHub releases to include release "assets". Since the zipball of the source code is already downloaded, it might be also worth looking at downloading and including the assets in the produced record.

File sizes are limited to 2GB per file, though there's no limit in the number of files, so soe checking is required before attempting to download the assets.

Feature request Needs investigation Pending GitHub

Source

slint

👍11

Most helpful comment

If by assets you mean additional files added to a release on GitHub before it is published, that would indeed be a great thing to have!

sdruskat on 12 Dec 2017

👍3

All 5 comments

If by assets you mean additional files added to a release on GitHub before it is published, that would indeed be a great thing to have!

sdruskat on 12 Dec 2017

👍3

Pinging in this issue with an use case: I have a repo for my thesis, and on a new release a PDF with the rendered content is uploaded to the release using GH actions.

I would like to see it show up in the Zenodo record, in the "Files" section.

luizirber on 21 Sep 2020

👍1

Adding another use case: I have a project for a mathematical model of the AV node which includes reference simulation results as a git submodule. Since GitHub does not include the contents of submodules in the automatically generated zip file of the repository, I have set up a Travis CI script that builds a zip file, which also includes these additional files and is automatically added to the release when a new tag is published.

It would be really nice if this zip file would show up on Zenodo, since automating Zenodo publications was the reason why I added this to the CI script in the first place.

CSchoel on 26 Nov 2020

Pinging in this issue with an use case: I have a repo for my thesis, and on a new release a PDF with the rendered content is uploaded to the release using GH actions.

I would like to see it show up in the Zenodo record, in the "Files" section.

Same for me.

vivi90 on 15 Apr 2021

This also helps with computer science conferences that evaluate artifacts. I have code in repo that generates this artifact, and could attach it to a release as well.