Github actions provides a token to actions with a set of permissions, however the docs have this little tidbit:
When you use the repository’s
GITHUB_TOKEN
to perform tasks, events triggered by theGITHUB_TOKEN
, with the exception ofworkflow_dispatch
andrepository_dispatch
, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs.
Which makes some sense, you might accidentally eat up every minute of actions time you have.
But it means that doing something like creating a deployment from one workflow then listening on on: deployment
in another workflow will not work.