timothy
6c470e769a
Build ErsatzTV Image / Delimiter ban (release path) (pull_request) Successful in 22s
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 18s
PR Gates / Docs update reminder (pull_request) Successful in 31s
PR Gates / Fix proofs (Proves trailers) (pull_request) Successful in 25s
PR Gates / decisions lifecycle (pull_request) Successful in 20s
PR Gates / Script lint and tests (ruff + pytest) (pull_request) Failing after 10s
review-verdict/h10 Awaiting review verdict for 6c470e7
Review verdict / Set review-verdict status (pull_request_target) Successful in 31s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Canceled after 1m28s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Canceled after 0s
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Canceled after 0s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Canceled after 0s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Canceled after 0s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Canceled after 0s
The previous probe reddened `Lint scripts (ruff check)` on F401 and the job stopped there, so `Lint scripts (ruff format --check)` had still never executed on the runner — merged is not ran, and a step nobody has seen run proves nothing. This probe is check-CLEAN and format-DIRTY, so the run reaches the second step. Both probes are reverted in the next commit. Refs: #780
8 lines
290 B
Python
8 lines
290 B
Python
"""TEMPORARY (#780) — a FORMAT-only violation, so `ruff format --check` is witnessed red too.
|
|
|
|
`ruff check` is clean on this file: the double space is a formatting issue, not a lint rule here.
|
|
Removed in the next commit. If you are reading this on main, the removal was lost.
|
|
"""
|
|
|
|
x = 1
|