Hi,

Many thanks for your feedback!  

Events raised from the Actions app do not trigger workflows.  This restriction is currently in place in order to prevent a circular workflow execution.  

Here is a similar ticket with more details, please kindly check, thanks.

In this case I’m not creating the original check_run or check_suite with github actions, that should be coming from TravisCI.

Ahh, that explains things, thanks!

@weide-zhou Am I reading this wrong, or does the official github documentation list “check_suite” as a valid action to listen against? It seems there are many tickets (like the one below) logged against similar issues. I’m confused why the documentation isn’t updated with this information clarifying that it is not supported.

https://github.community/t5/GitHub-Actions/Can-you-use-Checks-API-Actions-to-trigger-new-workflows/td-p/32704

To clarify, I am trying to do something like this within a local branch:

name: 'Listen to check_suite'
on:
  check_suite:
    types: [rerequested, completed]
jobs:
  job-that-listens-to-check-suite:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: 'attempt step'
         uses: ./.github/actions/my-local-action

 When I listen to a different event (e.g. pull_request) the action fires properly, but the check_suite event never fires, even though it is triggered by a manual “git push” from myself (which I would think would be considered as not sourced by the “github actions” app). Is it expected behavior for the check_suite event not to be received in this situation by my github workflow?

Are there any situations where “check_suite” would trigger a workflow or is the documentation wrong and it’s not actually supported?