:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
workflow-plan
Evaluates the if: conditions in .github/workflows/*.yml and .depot/workflows/*.yml the way GitHub does, against synthetic PR, push, schedule, and cancellation scenarios, and reports which jobs and steps run.
The evaluator is GitHub's own @actions/expressions, so operator precedence, coercion, contains, fromJSON, and the labels.*.name filter syntax behave as they do in Actions.
See a workflow's run plan
hogli ci:plan .depot/workflows/ci-backend.yml
hogli ci:plan .depot/workflows/ci-backend.yml --steps changes
The table has one row per job and one column per built-in scenario: draft, ready, and fork pull requests, a queued merge-queue run, a merged push to master, a scheduled run, and a dispatched run.
A cell reads ▶ for a job that runs, ✗ for one that fails, ⊘ for one that is cancelled, and . for a skipped job; a trailing 0 marks a matrix that expands to no cells. A job with continue-on-error: true that fails shows ✗, while its dependents read needs.<job>.result as success, as on GitHub. A legend under the table repeats this.
In a terminal the header row is bold and every second row has a shaded background; set NO_COLOR to turn that off.
Every paths filter is stubbed as if all of its filters matched.
Outputs that scripts produce at runtime are empty, so a job gated on needs.x.outputs.matrix != '' shows as skipped and a matrix built from such an output has no cell count.
Where a workflow cannot be planned without such a value, SCRIPT_STUBS in src/scenarios.ts supplies it per workflow path, for example the release plan output.
Pin the intended behavior in a test
hogli test:workflows
tests/workflows.test.ts names the jobs that must run or skip for each workflow and scenario.
The expectations follow the authoring skill.
They cover draft and merge-queue matrices, fork telemetry, no-ci draft gates, hourly runs, and cancellation verdicts.
Every job with an if: in .depot/workflows/ci-backend.yml or ci-frontend.yml must appear in at least one expectation.
The coverage test fails when a new conditional job has no expectation.
A smoke test also feeds every workflow through the built-in scenarios and fails on any condition the evaluator rejects.
Add a row when you add or change a condition. A row needs three things:
backend(
{ name: 'draft PR', github: pullRequest({ draft: true }) },
{
runs: ['changes', 'django', 'django_tests'],
skipped: ['turbo-tests'],
}
)
github: the event, frompullRequest(),mergeQueue(),push(),schedule(), orworkflowDispatch()insrc/scenarios.ts.steps: stubbed step outputs by job id and step id (or step name), for the paths filter and selector scripts.allFiltersChanged(workflow)stubs every filter as matched;pathsFilter({ backend: false })narrows one.runs,skipped,results: the jobs to assert on.resultstakes the exact outcome, which is how a gate is checked forcancelledon a superseded run.
A cancelled run is modeled as cancelled before any job starts, except the jobs listed in completedBeforeCancel, which plan as if the run were live.
That is how the self-cancel in ci-backend.yml is tested: repo-checks completes with a failing step, the run cancels, and the gate still runs because its OR-ed deterministic_failure disjunct is true.
What it does not model
- Trigger-level
on.<event>.paths,branches, andtypesfilters. A scenario assumes the workflow was dispatched. - Concurrency groups and
cancel-in-progress. - Matrix expansion beyond a cell count, which the CLI prints as
0when a job's matrix resolves to no cells. - Anything a
run:body does. Step outputs come only from stubs. - Reusable-workflow calls are planned as one job. Stub their outputs with
jobOutputs.