Push new versions of GliderTools to zenodo

[callumrollo]

Using GitHub actions, a new release will automatically trigger a build on PyPI for the new package.

https://github.com/GliderToolsCommunity/GliderTools/blob/master/.github/workflows/pythonpackage.yml

The release instuctions repo states that, after a new release "The DOI will also be updated on Zenodo". Is there a method to achieve this? Currently, the last version on zenodo is 2021.05.26 How do we get the new release 2022.12.13, and future releases, on to zenodo?

@jbusecke @tjryankeogh @lukegre

[jbusecke]

I was just looking into this, and noticed that our zenodo badge is also broken.

What I can see from the settings is that there is no webhook to zenodo

Who set the zenodo-github integration up in the first place? @lukegre

[jbusecke]

I wonder if there is a way to transfer the zenodo account to the github org. Having one persons account linked to this seems bad in the long run.

[callumrollo]

Some kind of group ownership on zenodo would be appreciated. Especially as the author list will keep expanding. The zenodo badge will be fixed in PR #161

[jbusecke]

I am unfortunately quite busy with other things atm. But if someone is able to find out how to arrange this and there is action needed from my end, please ping me.

[jbusecke]

I just checked on my zenodo account and found this:

I do not remember to have turned of this integration! But maybe this will allow others to just set it up with the org....

[callumrollo]

Thanks for following this up Julius. It's not time a sensitive issue, hardly anyone has downloaded glidertools from zenodo. It would be nice to (re)enable it as an automatic hook if possible though.