GitHub Actions Trigger Simulator

Will this workflow actually run? Paste your on: config, pick an event, set the ref and changed files, and get a definitive verdict plus the rule that decided it.

GitHub evaluates triggers in a specific order: the event must be configured, then branches/tags filters gate the ref, then paths/paths-ignore gate the changed files. This simulator runs that logic using the same glob engine as the paths filter tester, so you can find out why a workflow did or did not fire.

The trigger rules it evaluates

• The event must be a key under on: or the workflow will not run.
• branches/branches-ignore gate branch pushes; tags/tags-ignore gate tag pushes (a branch filter never matches a tag push).
• paths requires at least one changed file to match; paths-ignore skips only when every changed file matches.
• An absent filter never blocks; an empty event config (e.g. pull_request: {}) runs unconditionally.

Debug a skipped run

When a workflow unexpectedly did not start, the deciding rule is usually a branches or paths filter. Reproduce the event here to see the exact filter that excluded it.

Related guides