Skip to content

feat: registry file_triggers map changed paths straight to journeys (#118) - #146

Merged
inth3shadows merged 2 commits into
mainfrom
feat/118-journey-file-triggers
Oct 30, 2026
Merged

inth3shadows merged 2 commits into
mainfrom
feat/118-journey-file-triggers

Conversation

@inth3shadows

Copy link
Copy Markdown
Owner

Fixes #118. Also fixes #136 and #138.

Reviewed by /code-review and a code-reviewer agent. The high-severity findings are fixed in e7f754f; the rest are filed as #142–#145.

…118)

`"file_triggers": {"<glob>": ["J1", ...]}` declares dependencies the graph
cannot model (SQL migrations -> RLS). Globs are repo-relative, whole-path,
`**` / `*` / `?`, matched against every raw diff path before the product
filter. Additive: a graph-selected journey gains `triggered_by`; a
trigger-only journey gets a confident `file-trigger` row. A matched
unmodeled path is declared covered and no longer forces the #117
all-journeys fallback; an unmatched one still does. Invalid triggers
(bad glob, empty list, unknown journey id) BLOCK.

In passing: #136 caps the unmodeled-path list in its warning; #138 gives
unmodeled fallback rows their own reason and warning.
…export map (#118 review)

- H1: export lists file_triggers in the map (## File triggers) and the
  --json sidecar, and refuses an invalid trigger like select does; the
  verify skill unions matching triggers into the set.
- H2: a glob with an empty, `.` or `..` segment, or `**` inside a segment,
  can never match a file and now BLOCKs instead of dropping the declared
  journeys behind a clean NONE.
- H3: a trailing `**` matches a path containing a newline.
- H4: at most two `**` segments per glob; more backtracked for >20s.
@inth3shadows
inth3shadows merged commit 9634298 into main Oct 30, 2026
5 checks passed
@inth3shadows
inth3shadows deleted the feat/118-journey-file-triggers branch October 30, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

select: the unmapped warning lists every unmodeled path uncapped P1: Journey-level file glob triggers for migrations and other non-indexed changes

1 participant