-
Good day, I have workflow in my repo to trigger build on push (including tags). When I create and push tags from my laptop it’s triggered just fine. What am I missing? My manual workflow is below. Using the same
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
The documentation on Using the
It you want the push to trigger a new workflow you need to use a PAT (personal access token) for authentication instead. Or you could try adding a |
Beta Was this translation helpful? Give feedback.
-
By default, the checkout action uses ${{ github.token }} (that is the GITHUB_TOKEN) as the authentication token, and set persist-credentials as true. As @airtower-luna mentioned, the GITHUB_TOKEN can’t trigger new workflow run, you need to use a personal access token (PAT). In your case, if you want to trigger the workflow with the push, you can try like as this:
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the quick and educating responses. I chose to use |
Beta Was this translation helpful? Give feedback.
-
Unfortunately my conclusions were premature:
So I’m back to square one 😑 |
Beta Was this translation helpful? Give feedback.
-
After more research, using a deploy key results in quite reasonable setup to achieve what I want:
Here is the full workflow:
Thank you all again for the information provided. |
Beta Was this translation helpful? Give feedback.
After more research, using a deploy key results in quite reasonable setup to achieve what I want:
DEPLOY_KEY_CI_TAGGING
GH SecretHere is the full workflow: