GitHub Actions trigger checker

io.github.Lawatch由 GitHub 账号 Lawatch 发布v1.0.0更新于 Nov 17, 2026

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

发布方自己的服务:check.tattoo: tattoo size and placement guide

已验证STDIO仅桌面效率与工作流开发者工具

概览

AI 生成的概览

判断某次 push 或 pull request 是否会触发指定的 GitHub Actions 工作流,并指出是哪一行过滤条件决定的。离线运行。

可以做什么
  • 用一次 push 或 pull request 检验单个工作流,返回是否运行、逐步推理、起决定作用的行与模式,以及每个文件在路径过滤下的结果
  • 针对同一事件检查仓库内所有工作流,列出哪些会运行、哪些不会
  • 用名称测试分支、标签或路径模式,给出起作用的模式与对应的正则表达式
  • 给出警告,例如 300 文件差异上限、只含忽略项的模式列表、无效过滤条件
适用场景
适用于工作流没有触发、需要查明原因时,或在修改 on: 过滤、路径过滤、活动类型之前做验证。也可用于一次性核对整个仓库的工作流对某次 push 或 pull request 的反应。
运行要求
以本地进程运行:Claude Desktop 安装包、Docker 镜像,或 Node.js 18+ 从源码启动。仓库级检查需要读取项目的 .github/workflows/ 目录。未声明账号、密钥或环境变量。
安装前请注意
README 称其只读且离线,不向任何地方发送数据。结果是近似判断:GitHub 的匹配器未公开,只评估 push、pull_request 与 pull_request_target 的过滤条件,也不评估作业级 if 条件,因此应作为参考而非确定结论。

安装

在 SourceWeft 中

  1. 打开 控制台中的 GitHub Actions trigger checker,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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).

来源:products/mcp/gha-trigger-check/README.md,提交 6e1ca13

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.0.0最新Nov 17, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Check 集成