Add DOI badge and automated release #404
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed with @alinelena and @ilyes319, adds release workflow to automate releasing on tagged commits.
Tested on my fork: https://github.com/ElliottKasoar/mace/releases
Once set up, each release would then be preserved via zenodo (see GitHub / Zenodo instructions).
An admin of the repository can reserve a DOI, so we can update the placeholders in the README before the next release, which should then immediately link correctly.
It would also be relatively straightforward to extend this workflow e.g. to use different build systems, or release to PyPI etc.
(Note: this also bumps versions in other GitHub Actions, but this can be separated/removed if preferable)