Devops: add GitHub Actions workflow for continuous deployment #123
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
This workflow will be triggered when a new tag is pushed that matches a semantic versioning pattern. If it is pushed to the main repository of the `aiidateam` account, a Python script `validate_release_tag.py` is run that will parse the `__version__` attribute of the package and compare it to the version of the tag. If they don't match, the workflow is aborted. Otherwise, the pre-commit and the unit test suite is ran, and when successfull, `flit` is used to build and publish the package to PyPI.
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.
This workflow will be triggered when a new tag is pushed that matches a
semantic versioning pattern. If it is pushed to the main repository of
the
aiidateamaccount, a Python scriptvalidate_release_tag.pyisrun that will parse the
__version__attribute of the package andcompare it to the version of the tag. If they don't match, the workflow
is aborted.
Otherwise, the pre-commit and the unit test suite is ran, and when
successfull,
flitis used to build and publish the package to PyPI.