Support the use of Deploy-Keys for push
Opened this issue · 1 comments
What you want to add
Currently, GITHUB_TOKEN is used for authentication while pushing tags. This issue is for requesting a feature to support the use of deploy keys for pushing tags from the workflow.
Why this is needed
From github documentation:
When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.
This is a problem if the tag event is supposed to trigger any other workflows. - [Ref]
A proposed solution for this is to use the deploy keys for pushing the tag. - [Ref1], [Ref2]
For any users who hit this issue:
Probably a better solution to this might be to reuse the existing workflows so that they can be called from other workflows. This requires modifying the existing workflows though.
For the owners of this action:
It would be a nice-to-have feature to allow pushing tags using deploy-keys.