[GH-ISSUE #634] Issue: #415

Closed
opened 2026-03-01 21:43:10 +03:00 by kerem · 2 comments
Owner

Originally created by @spielhoelle on GitHub (Apr 23, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/634

Act version

act version 0.2.20

Expected behaviour

act -l should show available jobs while using on: [repository_dispatch] without invoking explicit trigger. With act repository_dispatch it works

Actual behaviour

act -l is not showing available jobs when using on: [repository_dispatch] and not infers the only event in my workflow.

Workflow and/or repository

workflow
name: deploy
on: [repository_dispatch] # doesn't work. `on: [push, repository_dispatch`]` works
jobs:
  deploy-remote-repo:
    runs-on: ubuntu-latest
    steps:
      - name: Event Information
        run: |
          echo "Event '${{ github.event.action }}' received from '${{ github.event.client_payload.repository }}'" 
      - name: Checkout Repo
        uses: actions/checkout@v2
      - name: Run playbook
        if: github.event.action == 'trigger_deploy'
        uses: saubermacherag/ansible-playbook-docker-action@v1.3
  [...]

Steps to reproduce

act output

Log
$ act -l
ID  Stage  Name  
Originally created by @spielhoelle on GitHub (Apr 23, 2021). Original GitHub issue: https://github.com/nektos/act/issues/634 <!-- - Make sure you are able to reproduce it on the [latest version](https://github.com/nektos/act/releases) - Search the existing issues. - Refer to [README](https://github.com/nektos/act/blob/master/README.md). --> ## Act version <!-- Paste output of `act --version` --> ```none act version 0.2.20 ``` ## Expected behaviour `act -l` should show available jobs while using `on: [repository_dispatch]` without invoking explicit trigger. With `act repository_dispatch` it works <!-- Describe how whole process should go and finish --> ## Actual behaviour `act -l` is not showing available jobs when using `on: [repository_dispatch]` and not infers the only event in my workflow. <!-- Describe what happened --> ## Workflow and/or repository <details> <summary>workflow</summary> ```none name: deploy on: [repository_dispatch] # doesn't work. `on: [push, repository_dispatch`]` works jobs: deploy-remote-repo: runs-on: ubuntu-latest steps: - name: Event Information run: | echo "Event '${{ github.event.action }}' received from '${{ github.event.client_payload.repository }}'" - name: Checkout Repo uses: actions/checkout@v2 - name: Run playbook if: github.event.action == 'trigger_deploy' uses: saubermacherag/ansible-playbook-docker-action@v1.3 [...] ``` </details> ## Steps to reproduce <!-- 1. use `on: [repository_dispatch]` 2. run `act -l` --> ## `act` output <!-- Paste output from your terminal, use `-v` or `--verbose` for richer output --> <details> <summary>Log</summary> ```none $ act -l ID Stage Name ``` </details>
kerem 2026-03-01 21:43:10 +03:00
Author
Owner

@catthehacker commented on GitHub (Apr 23, 2021):

The behaviour is correct.
https://github.com/nektos/act#commands
You can use --detect-event to not type specific event in act
https://github.com/nektos/act#flags

<!-- gh-comment-id:825940885 --> @catthehacker commented on GitHub (Apr 23, 2021): The behaviour is correct. https://github.com/nektos/act#commands You can use `--detect-event` to not type specific event in `act` https://github.com/nektos/act#flags
Author
Owner

@spielhoelle commented on GitHub (Apr 23, 2021):

Cool, didn't filter that out of the docs. Thank you

<!-- gh-comment-id:825941685 --> @spielhoelle commented on GitHub (Apr 23, 2021): Cool, didn't filter that out of the docs. Thank you
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/act#415
No description provided.