Repository navigation
Conversation
docs-static, doc-anchors and known-failures ran on every pull request, including PRs that touch nothing EQL reads. known-failures asks GitHub whether issues are open, so closing an issue could turn an unrelated PR red. The changes job now has a second dorny/paths-filter key, eql:, and a second output. The three jobs need changes and run off a pull request, or on one when eql is true. The key selects all of packages/eql/, because test:public_identifiers greps every tracked file there and test:doc-anchors reads every tracked markdown file. It also selects what the jobs read outside the subtree: the root mise.toml and its task includes (mise reads parent configs), and .cargo/config.toml, Cargo.toml and the five stack-* crates (docs:validate:source builds eql-codegen, which resolves the EQL workspace). The parity check now reads only relevant:. New checks pin the eql output's default on non-PR events, the three jobs' gate, and that the eql key selects every tracked file under the subtree and the parent-directory config. Claude-Session: https://claude.ai/code/session_016Usf7cQGY6ULWGyZ4NHQEB
|
|
Warning Review limit reachedOnly developers with an assigned seat can use this organization's usage-based review budget, and seats here are assigned manually. Ask an admin to assign a seat, or change the review continuation mode in Billing. Next included review available in 10 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (9)
Comment |
What
This PR gates the cheap EQL doc and known-failure jobs on a new path filter, so they skip pull requests that change nothing they read.
Why
docs-static,doc-anchorsandknown-failuresrun on every pull request, even one that touches nothing in EQL.known-failurescan fail a pull request that has nothing to do with EQL.relevantfilter is too narrow for these jobs, because they read files it leaves out, such aspackages/eql/AGENTS.md.How
changesjob has a neweql:filter key andeqloutput. The key selects all ofpackages/eql/and the workflow file.mise.tomland its task files.docs-staticruns cargo through thebuildtask, so the key also selects.cargo/config.toml,Cargo.tomland the stack crates that cargo loads.changes, and skips only on a pull request whoseeqloutput is false. On push and schedule runs,eqlis always true.relevant:with the push list. New checks make sure thateqldefaults to true off a pull request. They also make sure that the cheap jobs useeql, and that it selects every tracked EQL file and the parent config.AGENTS.mdno longer say that these jobs run on every pull request.🤖 Generated with Claude Code
https://claude.ai/code/session_016Usf7cQGY6ULWGyZ4NHQEB