Use a release workflow where the git tag is created locally rather than in the GitHub Action.
This would support the new "push a tag to trigger a release" workflow we have discussed.
✨ What's your proposed solution?
Create and push git tag if --git-tag is specified. The format of the tag would be v$NEW_VERSION.
I think we should create a signed tag:
git tag -s "v$NEW_VERSION" -m 'Release v$NEW_VERSION'
This will fail if the user hasn't configured their signing key, but I think that's fine. They should.
📚 Any additional context?
We're using "trigger by tag push" in cucumber/vscode because we had to use a 3rd party Action to be able to upload release assets, and this action expects to find the git tag in ${{ github.ref_name }}
🤔 What's the problem you're trying to solve?
Use a release workflow where the git tag is created locally rather than in the GitHub Action. This would support the new "push a tag to trigger a release" workflow we have discussed.
✨ What's your proposed solution?
Create and push git tag if
--git-tag
is specified. The format of the tag would bev$NEW_VERSION
. I think we should create a signed tag:This will fail if the user hasn't configured their signing key, but I think that's fine. They should.
📚 Any additional context?
We're using "trigger by tag push" in cucumber/vscode because we had to use a 3rd party Action to be able to upload release assets, and this action expects to find the git tag in
${{ github.ref_name }}