From 0fe78f9282df0b93d43e0f95148e493a95b05f05 Mon Sep 17 00:00:00 2001
From: Paul Osborne <paul.osborne@fastly.com>
Date: Wed, 3 Jun 2026 11:52:01 -0500
Subject: [PATCH] Update main CI job to have less ambigous name

Right now, GitHub is not showing an option in branch
protection rules for this job to be completed as a status check.
While I have not seen anything explicitly documented that having
unnamed or generic job ids (e.g. build) will cause this to happen,
there are recommendations to have jobs be uniquely named to
avoid ambiguity and potential problems.
---
 .github/workflows/python-ci.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/python-ci.yml b/.github/workflows/python-ci.yml
index 2a40d08..9674cb9 100644
--- a/.github/workflows/python-ci.yml
+++ b/.github/workflows/python-ci.yml
@@ -18,7 +18,8 @@ env:
   WASM_TOOLS_VERSION: "1.250.0"
 
 jobs:
-  build:
+  lint_build_test:
+    name: "Lint, Build & Test"
     runs-on: ubuntu-24.04
     steps:
     - uses: actions/checkout@v6