Community · E2 · artifact verified
Select which tests a change needs
A sibling GitHub Action that decides which allowlisted test groups a pull request needs and which can safely be skipped: the group list stays in your config, Jev picks among it, and deterministic rules a model cannot bypass have the final word.
01 · Role in the system
What Jev does here
Running every suite on every PR burns minutes and money, and letting an unconstrained model invent skip lists is unsafe. Test Intelligence keeps the group list in the repository's own config, sends the change context to Jev, and asks which allowlisted groups the change actually needs - the model cannot add a group that is not allowlisted. Deterministic rules are applied afterward, downstream jobs read the selected groups through if: conditions, and the Action never executes tests itself and never rewrites workflows. Part of a JevForge suite of typed-decision CI Actions with released versions and CI of its own.
02 · Control boundary
Where Jev sits
Allowlist-constrained choice over test groups; deterministic post-rules and if: gates downstream; the Action only decides, never executes.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Skip decisions are only as good as the group allowlist; a misgrouped test can be skipped for unrelated changes.
- Minutes-saved figures are not published; the value claim is structural rather than measured in the README.
- Node 24 runtime requirement is newer than many CI images ship by default.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- JevForge ↗Community · github · public · checked 2026-09-25