I believe that using both of the CI environments is a bit redundant. We could try to replicate the flow from Travis onto the Github actions by:
Creating a workflow that builds and runs the tests on all the branches on push and therefore running the semantic-release command.
Once this workflow is done we could run the publish for checking for new releases. (on release).
I believe that using both of the CI environments is a bit redundant. We could try to replicate the flow from Travis onto the Github actions by:
Creating a workflow that
buildsandruns the testson all the branches onpushand therefore running thesemantic-releasecommand. Once this workflow is done we could run thepublishfor checking for new releases. (on release).A similar approach on https://github.com/DHI-GRAS/gras-react-boilerplate/actions.