"deployment_status" isn't triggered #26178
-
Here’s a test case: https://github.com/wildpeaks/issue-deployment-status-action/tree/master/.github/workflows Two actions: - Deploy triggered by deployment (when a Deployment is created using Github API v3): this runs fine - Notify triggered by deployment_status: this doesn’t run Action Deploy sends a success status: - the Actions logs show the status was received successfully - the Environments tab shows the status change and says it’s deployed Yet the Notify action doesn’t show up in the Actions tab at all. However, I managed to isolate the cause to the token used to set the Status: - when using github.token , the status gets changed, but Notify isn’t triggered - when using a token from a user with write permission on the repo (the same one used to create the deployment), the status gets changed and Notify is triggered Is this by design ? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @cecilemuller , Yes, this is by design. With github token, an action in a workflow run can’t trigger a new workflow run. Please refer to official doc for more details. Creating personal access token as secrets instead is the workaround. Thanks. |
Beta Was this translation helpful? Give feedback.
Hi @cecilemuller ,
Yes, this is by design.
With github token, an action in a workflow run can’t trigger a new workflow run. Please refer to official doc for more details.
Creating personal access token as secrets instead is the workaround.
Thanks.