HAL9000
1297f093c3
CI / lint (pull_request) Successful in 56s
CI / typecheck (pull_request) Successful in 57s
CI / security (pull_request) Successful in 1m5s
CI / quality (pull_request) Successful in 51s
CI / push-validation (pull_request) Successful in 44s
CI / build (pull_request) Successful in 1m2s
CI / helm (pull_request) Successful in 1m8s
CI / unit_tests (pull_request) Successful in 4m40s
CI / docker (pull_request) Successful in 1m37s
CI / integration_tests (pull_request) Successful in 8m16s
CI / coverage (pull_request) Successful in 9m9s
CI / status-check (pull_request) Successful in 3s
The CREATE_TRACKING_ISSUE and CREATE_ANNOUNCEMENT_ISSUE scenarios in
features/automation_tracking_mandatory_labels.feature used Behave tables
without explicit column headers, but the step implementations index rows
by row["name"] / row["value"]. Behave was treating the first data row as
the heading row, raising KeyError('"value" is not a row heading') and
erroring both scenarios.
Add the missing `| name | value |` header row to both tables so the
indexed access works as written. Also apply `ruff format` to the steps
module to satisfy the lint/format gate (trailing commas in dict literals
and parenthesised long assert messages).
ISSUES CLOSED: #3105