Skip to content

Commit 2559607

Browse files
ci(e2e): add run-name to label E2E runs by mode
PR #275's summary described mode-labelled runs ("E2E — interactive", "E2E — interactive + smoke-all (nightly)", "E2E — recreate baselines") but no `run-name:` key was ever added — every run showed the static workflow name. Add run-name, branching on the trigger context: recreate-snapshots dispatch, schedule (nightly), run-smoke-all dispatch, or the default push/PR interactive gate.
1 parent 702c6ef commit 2559607

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

.github/workflows/hub-client-e2e.yml

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,20 @@
11
name: Hub-Client E2E Tests
22

3+
# Label runs by mode in the Actions UI. `run-name` is evaluated at workflow
4+
# top level with only the `github`/`inputs` contexts available, so it branches
5+
# purely on the trigger. Order matters — first truthy arm wins:
6+
# - recreate-all-snapshots dispatch → baseline regeneration
7+
# - schedule → nightly (interactive + smoke-all)
8+
# - run-smoke-all dispatch → on-demand interactive + smoke-all
9+
# - everything else (push/PR) → the fast interactive gate
10+
run-name: >-
11+
${{
12+
inputs.recreate-all-snapshots && 'E2E — recreate baselines'
13+
|| github.event_name == 'schedule' && 'E2E — interactive + smoke-all (nightly)'
14+
|| inputs.run-smoke-all && 'E2E — interactive + smoke-all'
15+
|| 'E2E — interactive'
16+
}}
17+
318
on:
419
workflow_dispatch:
520
inputs:

0 commit comments

Comments
 (0)