Push from workflow not doesn't trigger on.push.tags workflow #27194
-
I have a workflow that triggers on push branches:
Now the job is successful, the push tag step is successful, and I see the tag in the remote repository. However, a subsequent workflow to publish does not get triggered:
If I manually create a tag and push it to the remote, the on.tags workflow will trigger. I believe this is related to some internal Actions mechanism as to avoid workflow infinite loops. I realize I could be butchering the adoption of Actions with this approach. any ideas or suggestions as to how to properly adopt this type of workflow using Actions, where one workflow creates a tag and pushes it back to its repository, which can then be observed and trigger another flow? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
By default,
If you want the push to create new workflow runs you need to use a PAT instead. After adding it as a secret you can do something like this to use it instead of
|
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply. It seems inappropriate for a CI job to use a PAT. If I leave the organization, the workflow will just start failing. I guess I’ll try to figure out another way to trigger or just combine the workflows. |
Beta Was this translation helpful? Give feedback.
By default,
actions/checkout
configuresGITHUB_TOKEN
for authentication. The problem is that events caused byGITHUB_TOKEN
cannot trigger new workflows as described in Using theGITHUB_TOKEN
in a workflow:If you want the push to create new workflow runs you need to use a PAT instead. After adding it as a secret you can do something like this to use it instead of
GITHUB_TOKEN
: