createGithubReleases: false disables git tag pushes too which is undocumented, and imo unexpected.
The docs say:
- createGithubReleases - A boolean value to indicate whether to create Github releases after
publish or not. Default to true
There are no mention of git tags.
When using git-cli mode, the tags are created locally. But they are not pushed. One would have to manually push them afterwards by checking the outputs.published value. But this feels like a bug and not an intended behaviour.
When using the github-api mode, the tags are not created locally, because they would be created via the API, which also does not happen for the above reason.
I would like to use the action to create the git tags, so that another action which has the on: push: tags trigger can run the deployment, which currently is only possible with the git-cli method if you do not want the action to publish releases too.
createGithubReleases: falsedisables git tag pushes too which is undocumented, and imo unexpected.The docs say:
There are no mention of git tags.
When using
git-climode, the tags are created locally. But they are not pushed. One would have to manually push them afterwards by checking theoutputs.publishedvalue. But this feels like a bug and not an intended behaviour.When using the
github-apimode, the tags are not created locally, because they would be created via the API, which also does not happen for the above reason.I would like to use the action to create the git tags, so that another action which has the
on: push: tagstrigger can run the deployment, which currently is only possible with thegit-climethod if you do not want the action to publish releases too.