This might require a separate pipeline. The idea is that, while everything in trunk should always be in "release-ready" state, we might not want to release every single merge. Pushing tags to trunk gives us the opportunity to define a separate GitHub Action with permission to post its built artifacts to the GitHub API in order to create a release.
calebwherry
commented
3 years ago
This might require a separate pipeline. The idea is that, while everything in
trunkshould always be in "release-ready" state, we might not want to release every single merge. Pushing tags to trunk gives us the opportunity to define a separate GitHub Action with permission to post its built artifacts to the GitHub API in order to create a release.