Right now creating a new release requires manually updating the package.json and then creating the release on GitHub.
Instead, we should create a GitHub workflow similar to update that uses the create-release action or something similar. Whenever a user has added enough new treebanks they're ready to create a release, the user could then use the GitHub Actions interface the same way this action is used.
Doing this might even be a way to get around the issue with the GitHub Zenodo integration not generating a DOI until after the archive is created. The "new release" action could use the Zenodo API to pre-reserve a DOI, update src/config.json, commit and push, then create a release on GitHub.
zfletch
commented
4 years ago
Right now creating a new release requires manually updating the
package.jsonand then creating the release on GitHub.Instead, we should create a GitHub workflow similar to
updatethat uses the create-release action or something similar. Whenever a user has added enough new treebanks they're ready to create a release, the user could then use the GitHub Actions interface the same way this action is used.Doing this might even be a way to get around the issue with the GitHub Zenodo integration not generating a DOI until after the archive is created. The "new release" action could use the Zenodo API to pre-reserve a DOI, update
src/config.json, commit and push, then create a release on GitHub.(From this conversation)