Skip to content
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

Automate draft release / historical database upload #45

Open
khaeru opened this issue Nov 24, 2020 · 0 comments
Open

Automate draft release / historical database upload #45

khaeru opened this issue Nov 24, 2020 · 0 comments
Labels
ci Continuous testing, integration, & other automation enh Enhancements & new features

Comments

@khaeru
Copy link
Contributor

khaeru commented Nov 24, 2020

Use actions/upload-release-asset and possibly actions/create-release to:

  • Automatically create a GitHub release in draft state on a new tag like v*.
  • Attach the (compressed) CSV version of the historical database as an asset associated with the release.

This will streamline the process of creating new Zenodo records that contain the latest database: after the above steps are done automatically, the release can be checked and taken out of draft state via the web interface. Then Zenodo will archive the repository, which should include the CSV asset.

@khaeru khaeru added enh Enhancements & new features ci Continuous testing, integration, & other automation labels Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous testing, integration, & other automation enh Enhancements & new features
Projects
None yet
Development

No branches or pull requests

1 participant