Per https://help.github.com/en/articles/events-that-trigger-workflows, workflows cannot trigger other workflow runs when using GITHUB_TOKEN:
> An action in a workflow run can’t trigger a new workflow run. For example, if an action 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.
I’m curious if this is a temporary limitation, and if this will be removed in the future. I can understand the reasoning for it, but it’s limiting for certain types of things that can be automated.
One example is using the deployments API with Actions. I’d like to build one workflow that handles
/deploy comments in PR’s to create GitHub Deployments, and then have another workflow that handles them. As of right now, that’s not possible if the workflow that creates the deployment uses GITHUB_TOKEN.
The only way to work around this right now is the either 1) create a bot user and use a personal access token or 2) create a github app. Both of these are cumbersome, and suck for various reasons.