Closed kvashchuka closed 3 years ago
This is a very welcome change 👏 Keen on getting away from Travis! However, currently the PyPI packages are built using Travis. Hence, we need to move that logic into Github Actions also...
Thank you, will add the workflow for that:)
Workflow is added, but for it to work a secret with API token from PyPi needs to be added to the repo and I don't have rights to do it. Could maybe one of the maintainers (@markusdregi or @jondequinor) do it?
I've now added a PYPI_SECRET
👍 Let us try to merge this and make a new release.
Could you add an entry in the release notes about moving replacing the Travis CI?
The release notes are written here: https://github.com/equinor/configsuite/blob/master/docs/source/release_notes.rst and new entries are added under the dev
section under a fitting section title. The available section titles are written at the top of the document as a comment (in the raw version).
I'm suggesting something along the lines of:
Miscellaneous
- Stop running CI on Travis and move PyPI deploy to GitHub Actions
Yes, I just figured it out when I saw your comment:) Could you also change settings such that travis-ci is not required for merge anymore?
Delete Travis CI as we do not intend to use it anymore