GitHub Actions trigger checker

io.github.LawatchPublished by GitHub account Lawatchv1.0.0Updated Nov 17, 2026

Will this GitHub Actions workflow run for this push or PR? Which filter line decides, and why

The publisher's own server: check.tattoo: tattoo size and placement guide

Overview

AI-generated overview

Explains whether a GitHub Actions workflow will run for a given push or pull request, and which filter line decides. Runs offline.

What you can do
  • Check one workflow against a push or pull request and get runs true/false, step-by-step reasoning, the deciding line and pattern, and per-file path decisions
  • Check every workflow in a repository for one event and see which run and which do not
  • Test branch, tag or path patterns against names, with the deciding pattern and the exact regular expression
  • Report warnings such as the 300-file diff limit, ignore-only lists and useless filters
When to use it
Useful when a workflow did not fire and you need to know why, or before merging a change to on: filters, path filters or activity types. Also handy for checking a whole repository's workflows against one push or pull request.
Requirements
Runs as a local process: a Claude Desktop bundle, a Docker image, or Node.js 18+ from source. For the repository-wide check, read access to the project's .github/workflows/ directory. No accounts, keys or environment variables declared.
Before you install
Read-only and offline per the README; nothing is sent anywhere. It is an approximation: GitHub's matcher is not public, only push, pull_request and pull_request_target filters are evaluated, and job-level if conditions are not evaluated, so treat answers as guidance rather than certainty.

Installation

In SourceWeft

  1. Open GitHub Actions trigger checker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

gha-trigger-check — MCP server

Why didn't my GitHub Actions workflow run? Will this push or pull request trigger it? Give the workflow and the push or pull request (branch or tag, changed files, activity type, commit message): the server says yes or no, explains each step, and names the workflow line and pattern that decide. Offline.

One-click install for Claude Desktop, VS Code and Cursor: https://lawatch.github.io/10aday/mcp/gha-trigger-check/
Question, wrong answer or missing case? Open an issue — we read them.

AI assistants answer these questions from memory, and the rules have traps:

  • branches: ["feature/*"] does not match feature/login/v2: * stops at /. Use feature/**.
  • With branches and ! exceptions, the last matching pattern wins: order matters.
  • On pull_request, branch filters are compared with the base branch (the target), not the PR branch.
  • on.push with only branches never runs for a tag push (and only tags never runs for a branch push).
  • paths filters are not evaluated for tag pushes; paths-ignore skips the run only if every changed file is ignored.
  • Default pull_request types are opened, synchronize, reopened: labeled or closed need types:.
  • [skip ci], [ci skip], [no ci], [skip actions], [actions skip] or a skip-checks: true trailer skip push and pull_request runs.
  • More than 3 tags pushed at once: no push event at all. A pull request with a merge conflict: no pull_request run.
  • branches together with branches-ignore (or paths with paths-ignore) makes GitHub reject the whole file.

Tools

ToolWhat it does
will_workflow_runOne workflow (YAML text or path) and one push / pull request. Returns runs (true, false, or null with the missing input), the reasoning step by step, the deciding line and pattern, per-file decisions for path filters, and warnings (300-file diff limit, !-only lists, useless filters).
which_workflows_runEvery workflow of the repository (given as contents, or read from .github/workflows/) for one push or pull request: which run, which do not, and why.
test_filter_patternsTest branch, tag or path patterns against names: selected or not, which pattern decides, the exact regular expression, and GitHub's error for an invalid pattern.

Example

json
{ "name": "will_workflow_run", "arguments": {  "workflow": "on:\n  push:\n    branches: [main, 'releases/**', '!releases/**-alpha']\n    paths: ['src/**', '!src/**/*.md']\n",  "branch": "main", "changed_files": ["src/api/README.md", "docs/setup.md"] } }

Result: runs: false. Branch main matches line 3, but no changed file is selected by paths: src/api/README.md is excluded again by !src/**/*.md.

How exact is it?

The pattern engine is a line-by-line port of pkg/workflowpattern from nektos/act (the tool that runs GitHub Actions locally), itself written from GitHub's documented filter syntax and cheat sheet. test.js builds act's Go code and compares both on random patterns and names (*, **, ?, +, ranges, !, escapes, invalid patterns): 300,000 cases, 0 differences. 4,000 recorded answers stay in fixtures.json. The event rules (branch vs tag filters, base branch, types, [skip ci], 3 tags, merge conflicts) follow GitHub's "Workflow syntax" and "Events that trigger workflows" docs, with 32 test cases. Checked on 68 real workflows (Vite, React, Next.js, Node.js, Rust, CPython, Deno...).

Limits: GitHub's own matcher is not public. A ! pattern inside a *-ignore list is undocumented: the server applies "last match wins" and warns. Only push, pull_request and pull_request_target filters are evaluated; other events are only checked for presence. Job-level if: conditions are not evaluated.

Install

  • Claude Desktop: open gha-trigger-check-1.0.0.mcpb from the GitHub release.
  • Any MCP client (Docker, read access to the project for which_workflows_run): {"command": "docker", "args": ["run", "-i", "--rm", "-v", "${workspaceFolder}:${workspaceFolder}:ro", "-w", "${workspaceFolder}", "ghcr.io/lawatch/gha-trigger-check:1.0.0"]}
  • From source (Node 18+, no install): {"command": "node", "args": ["/path/to/server.js"]}

Offline, read-only, nothing is sent anywhere.

Licenses

Server code: MIT. Bundled unchanged: yaml 2.9.1 (ISC, Eemeli Aro), license in vendor/. Pattern engine ported from nektos/act (MIT).

Built by AI agents (project 10aday).

Source: products/mcp/gha-trigger-check/README.md at commit 6e1ca13

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestNov 17, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Check integrations