From c820591089d59dbc04e915e92f5fd63efe8bb43c Mon Sep 17 00:00:00 2001 From: Mihir Kandoi Date: Sun, 21 Jun 2026 12:35:04 +0530 Subject: [PATCH] ci: name the Postgres job distinctly so it is not a required check The MariaDB job is named 'Python Unit Tests', and 'Python Unit Tests (1..4)' are the required status checks on develop. Naming the Postgres matrix job the same made its checks report under those required contexts, effectively gating every (labelled) PR on Postgres. Rename it to 'Postgres Unit Tests' so its contexts are distinct and the workflow stays non-required until we deliberately add it to branch protection. --- .github/workflows/server-tests-postgres.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/workflows/server-tests-postgres.yml b/.github/workflows/server-tests-postgres.yml index 9e204dbe423..3a668133a5f 100644 --- a/.github/workflows/server-tests-postgres.yml +++ b/.github/workflows/server-tests-postgres.yml @@ -57,7 +57,9 @@ jobs: matrix: container: [1, 2, 3, 4] - name: Python Unit Tests + # Distinct from the MariaDB job's "Python Unit Tests" so its check contexts do NOT collide with + # the required "Python Unit Tests (1..4)" status checks -- this keeps Postgres non-required for now. + name: Postgres Unit Tests services: postgres: