ci: a pull request runs only the journeys it can break (#1173) #1174

Merged

claude-bot merged 2 commits from ci/1173-fewer-journeys into main 2026-10-13 16:35:36 +00:00

Conversation 0 Commits 2 Files changed 3 +84 -3

claude-bot commented 2026-10-13 16:00:29 +00:00

Collaborator

Copy link

Options 1, 2 and 4 of #1173 (and most of 3, since a Renovate PR is a pull request like any other). Options 5 and 6 are not in this change.

A new job, Which journeys does this change need?, decides the journeys matrix, in the shape audio_paths already uses:

Run	Journeys
push to main, manual dispatch	all three projects
PR from a chore/release-* branch	all three
PR touching webapp/frontend/e2e/, scripts/journeys.sh, Dockerfile, a compose file, nginx.conf, package(-lock).json or ci.yml	all three
PR whose every file is under bot/, docs/, changelog.d/, tools/, webapp/backend/evals/, webapp/backend/tests/, .claude/, or is a top-level .md	none (job skipped)
any other PR	desktop only
the diff cannot be read	all three (fails open)

"Cannot affect" is an allow-list: a path not named runs the journeys.

One addition to the issue's option 1. A PR that adds or changes a spec still runs all three. On 12 to 13 Oct, three new specs failed in one project only (a pointer click in the keyboard project, for one); those are caught on the PR, not on main.

Cost, as the issue says: a phone-only or keyboard-only regression in product code is now caught on the push to main, after the merge. A release PR runs all three, so it is caught before a tag at the latest.

Verified

• The workflow parses; journeys needs docker and the new job.
• The decision script, run locally against seven sample change lists plus the release-branch, push and unreadable-diff cases, gives the table above.
• This PR changes ci.yml, so its own run takes the all-three path through the dynamic matrix (fromJSON of a job output), which is the part not exercised before on this runner version.

Not verified: the desktop-only and skipped paths on a real run (the first ordinary PR after this merges will show them). Whether branch protection's CI / * accepts a run with no phone or keyboard check: audio_paths records that a skipped check is accepted, but absent matrix entries are a slightly different case.

🤖 Generated with Claude Code

Options 1, 2 and 4 of #1173 (and most of 3, since a Renovate PR is a pull request like any other). Options 5 and 6 are not in this change. A new job, `Which journeys does this change need?`, decides the `journeys` matrix, in the shape `audio_paths` already uses: | Run | Journeys | |---|---| | push to `main`, manual dispatch | all three projects | | PR from a `chore/release-*` branch | all three | | PR touching `webapp/frontend/e2e/`, `scripts/journeys.sh`, `Dockerfile`, a compose file, `nginx.conf`, `package(-lock).json` or `ci.yml` | all three | | PR whose every file is under `bot/`, `docs/`, `changelog.d/`, `tools/`, `webapp/backend/evals/`, `webapp/backend/tests/`, `.claude/`, or is a top-level `.md` | none (job skipped) | | any other PR | `desktop` only | | the diff cannot be read | all three (fails open) | "Cannot affect" is an allow-list: a path not named runs the journeys. **One addition to the issue's option 1.** A PR that adds or changes a spec still runs all three. On 12 to 13 Oct, three new specs failed in one project only (a pointer click in the keyboard project, for one); those are caught on the PR, not on `main`. **Cost, as the issue says:** a phone-only or keyboard-only regression in product code is now caught on the push to `main`, after the merge. A release PR runs all three, so it is caught before a tag at the latest. ## Verified - The workflow parses; `journeys` needs `docker` and the new job. - The decision script, run locally against seven sample change lists plus the release-branch, push and unreadable-diff cases, gives the table above. - This PR changes `ci.yml`, so its own run takes the all-three path through the dynamic matrix (`fromJSON` of a job output), which is the part not exercised before on this runner version. Not verified: the `desktop`-only and skipped paths on a real run (the first ordinary PR after this merges will show them). Whether branch protection's `CI / *` accepts a run with no phone or keyboard check: `audio_paths` records that a skipped check is accepted, but absent matrix entries are a slightly different case. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit 2026-10-13 16:00:29 +00:00

ci: a pull request runs only the journeys it can break (#1173) ... 2bfe45740d

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude-bot referenced this pull request 2026-10-13 16:00:38 +00:00

CI: limit how often the end-to-end journeys run while the runners are being fixed #1173

claude-bot scheduled this pull request to auto merge when all checks succeed 2026-10-13 16:02:04 +00:00

rbrooks added 1 commit 2026-10-13 16:02:52 +00:00

ci: the journeys plan sees renames and the whole backend tree (#1173) ... 528139ec88

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

claude-bot merged commit 650ed460dc into main 2026-10-13 16:35:36 +00:00

claude-bot deleted branch ci/1173-fewer-journeys 2026-10-13 16:35:37 +00:00

claude-bot referenced this pull request from a commit 2026-10-13 16:35:38 +00:00

Merge PR #1174: a pull request runs only the journeys it can break (#1173)

claude-bot referenced this pull request 2026-10-13 17:50:46 +00:00

fix(webapp): small things from the 4.5.1-rc1 render check (#1175) #1176

claude-bot referenced this pull request 2026-10-13 18:03:16 +00:00

fix(webapp): opening a thread marks it read by an explicit POST; a test pins which GETs may write (#1163) #1177

claude-bot referenced this pull request 2026-10-17 04:21:17 +00:00

CI: the journeys check names read "(desktop) (desktop)" #1203

claude-bot referenced this pull request 2026-10-27 17:38:39 +00:00

CI: build the end-to-end images once per run, and a teardown that survives a cancel #1248

claude-bot referenced this pull request 2026-10-27 17:38:52 +00:00

CI: limit how often the end-to-end journeys run while the runners are being fixed #1173

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

backend

Issue related to the backend

  

bot

Issue related to the bot

  

bug

Something is not working

  

duplicate

This issue or pull request already exists

  

enhancement

New feature

  

frontend

Issue related to the frontend

  

help wanted

Need some help

  

invalid

Something is wrong

  

question

More information is needed

  

recording

Issue related to the recording system

  

security

Security hardening / vulnerability work

  

wontfix

This won't be fixed

No labels

backend

bot

bug

duplicate

enhancement

frontend

help wanted

invalid

question

recording

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

rbrooks/Quest-Board!1174

No description provided.