wrkflw

mirror of https://github.com/bahdotsh/wrkflw.git synced 2026-07-10 20:40:26 +02:00

Files

Gokul 4a3c5b2e73 docs: catch up on everything that landed after v0.7.3 (#107 )

v0.7.3 was tagged back in August and then roughly fifty commits
happened. The docs, predictably, noticed none of this.

The README still advertised four TUI tabs when the TUI now has
seven, still listed three runtime modes when there are four, still
declared artifacts/cache/reusable-workflow outputs as "Not
Supported" when all three shipped in #88 and #94, and never
mentioned `wrkflw watch` or the `--event` / `--diff` /
`--changed-files` flags at all. `wrkflw-trigger-filter` and
`wrkflw-watcher` existed in the workspace without READMEs. Two of
the Rust examples referenced a `runtime` field on
`ExecutionConfig` that is actually called `runtime_type`, and
printed a `summary_status` field that doesn't exist. One
`run_wrkflw_tui` example was missing an argument. That kind of
thing.

While at it, BREAKING_CHANGES.md was labeling three entries as
"(v0.7.3)" when the underlying commits all landed *after* the
v0.7.3 tag — so calling them part of that release was, let's say,
a work of fiction. Relabel as "(Unreleased)" with a note up top
pointing at the next release.

New trigger-filter and watcher READMEs are deliberately short —
most users should hit that code through the CLI flags, not by
depending on the crates directly. No point padding them.

Nothing here is a code change. Just the docs finally telling the
truth about what's in the tree.

2026-04-21 23:43:11 +05:30

src

fix(executor): populate workflow-level env in expression context (#95 )

2026-04-14 10:11:10 +05:30

Cargo.toml

feat: add diff-aware selective execution and watch mode (#91 )

2026-04-11 20:27:34 +05:30

README.md

docs: catch up on everything that landed after v0.7.3 (#107 )

2026-04-21 23:43:11 +05:30

README.md

wrkflw-trigger-filter

Parses a GitHub Actions on: block and decides whether a workflow would fire for a given event context and changed file set. Powers wrkflw run --event … and wrkflw watch.

Parses push, pull_request, pull_request_target, workflow_dispatch, schedule, and the other documented GHA events
Matches branches, branches-ignore, tags, tags-ignore, paths, paths-ignore, and types: filters
Auto-detects the diff base (origin/HEAD, main, master, then HEAD~1) when invoked without an explicit base ref
Returns a structured reason on skip so the CLI/TUI can explain why a workflow was filtered out

Consumers: wrkflw CLI (run, watch) and wrkflw-watcher. Most users should reach this functionality through the --event / --diff flags rather than depending on the crate directly.