Tagging using release tools isn't running pipelines
Summary
Tagging using release tools isn't running pipelines
With the recent changelog changes to the helm release-tools I created this month, the order in which the commits happen during the release has changed. SO now the changelog is that last commit before tagging. This is a problem as the release-tools includes ci-skip in the commit message, so our tag pipeline ends up not running in CI.
We need to update the release-tools to ensure our tagged commit doesn't have ci-skip.
As a workaround, you can manually trigger pipelines from the GitLab UI for the tag. This is what I have done for the 1.1.0
release.