ci(e2e): drop the doubled E2E prefix from the published check names #481

Merged

nrupard merged 1 commit from fix/BUNYIP-478-e2e-check-name-dedup into main

2026-08-06 15:22:50 +02:00

nrupard commented

2026-08-05 21:51:56 +02:00

Owner

What

Fixes the doubled E2E check names introduced by #477. Forgejo publishes an Actions check as <workflow name> / <job name>, so putting E2E / in the job name too produced:

E2E / E2E / deployment (workflow E2E + job E2E / deployment)
E2E PR gate / E2E / PR gate (workflow E2E PR gate + job E2E / PR gate)

This sets both workflows' name: to E2E and the job names to just the second segment:

File	workflow `name:`	job `name:`	published check
e2e.yml	`E2E`	`deployment`	`E2E / deployment`
e2e-pr.yml	`E2E`	`PR gate`	`E2E / PR gate`

Why (BUNYIP-478)

A single E2E /* branch-protection pattern matches both, and the names read as intended. The two workflow files now share the E2E display name; their file paths, triggers (push/dispatch vs pull_request), and job names keep them distinct.

Scope

Names only. Triggers, job ids (e2e, e2e-pr), env: secret scope, and concurrency groups unchanged. check-workflow-secrets.sh and check-runner-labels.sh both pass.

Branch-protection reminder: require E2E / PR gate (or pattern E2E /*) on pull requests once this merges.

#BUNYIP-478

## What Fixes the doubled E2E check names introduced by #477. Forgejo publishes an Actions check as `<workflow name> / <job name>`, so putting `E2E /` in the job name too produced: - `E2E / E2E / deployment` (workflow `E2E` + job `E2E / deployment`) - `E2E PR gate / E2E / PR gate` (workflow `E2E PR gate` + job `E2E / PR gate`) This sets both workflows' `name:` to `E2E` and the job names to just the second segment: | File | workflow `name:` | job `name:` | published check | |---|---|---|---| | e2e.yml | `E2E` | `deployment` | `E2E / deployment` | | e2e-pr.yml | `E2E` | `PR gate` | `E2E / PR gate` | ## Why (BUNYIP-478) A single `E2E /*` branch-protection pattern matches both, and the names read as intended. The two workflow files now share the `E2E` display name; their file paths, triggers (push/dispatch vs pull_request), and job names keep them distinct. ## Scope Names only. Triggers, job ids (`e2e`, `e2e-pr`), `env:` secret scope, and concurrency groups unchanged. `check-workflow-secrets.sh` and `check-runner-labels.sh` both pass. Branch-protection reminder: require `E2E / PR gate` (or pattern `E2E /*`) on pull requests once this merges. #BUNYIP-478

nrupard added 1 commit

2026-08-05 21:51:56 +02:00

ci(e2e): drop the doubled E2E prefix from the published check names

E2E / PR gate (pull_request) Successful in 16s

Details

Check / fmt + clippy + build + tests (pull_request) Successful in 4m34s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

d85ba613e5

Forgejo publishes an Actions check as `<workflow name> / <job name>`. The prior rename (#477) put `E2E /` in the job name too, so the checks rendered doubled: `E2E / E2E / deployment` (workflow `E2E` + job `E2E / deployment`) and `E2E PR gate / E2E / PR gate` (workflow `E2E PR gate` + job `E2E / PR gate`).

Set both workflows' name to `E2E` and the job names to just the second segment (`deployment`, `PR gate`), so the checks render as the intended `E2E / deployment` and `E2E / PR gate`. A single `E2E /*` branch-protection pattern matches both. The two workflow files now share the `E2E` display name; their file paths, triggers, and job names keep them distinct.

Names only: triggers, job ids (`e2e`, `e2e-pr`), and secret scope are unchanged, and both workflow validators pass.

#BUNYIP-478