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 整合