From 37d85317bea776624432cbe500f204b6e096ad7b Mon Sep 17 00:00:00 2001
From: jon8787 <112368577+jon8787@users.noreply.github.com>
Date: Tue, 7 Jul 2026 11:55:34 +1000
Subject: [PATCH 1/2] UID2-7426: add check_jira_key required-status-check
 caller

---
 .github/workflows/check-jira-key.yaml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 .github/workflows/check-jira-key.yaml

diff --git a/.github/workflows/check-jira-key.yaml b/.github/workflows/check-jira-key.yaml
new file mode 100644
index 0000000..a233cda
--- /dev/null
+++ b/.github/workflows/check-jira-key.yaml
@@ -0,0 +1,19 @@
+# Roll out to each in-scope IABTechLab uid2* repo as .github/workflows/check-jira-key.yaml
+# once uid2-shared-actions #254 is merged AND a release has moved the v3 tag to include
+# actions/check_jira_key. Non-blocking until the terraform required_status_checks rule is flipped on.
+name: Check Jira Key
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  # Job name PINNED to `check_jira_key` so every repo produces the same status-check context
+  # ("check_jira_key") — one terraform required_status_checks entry matches all repos (UID2-7426).
+  check_jira_key:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: IABTechLab/uid2-shared-actions/actions/check_jira_key@v3

From 3f514827857c5c289a851b8bf9e04ec5a9654504 Mon Sep 17 00:00:00 2001
From: jon8787 <112368577+jon8787@users.noreply.github.com>
Date: Tue, 7 Jul 2026 13:07:37 +1000
Subject: [PATCH 2/2] UID2-7426: trim caller comment (drop stale rollout note;
 tighten job-name comment)

---
 .github/workflows/check-jira-key.yaml | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/check-jira-key.yaml b/.github/workflows/check-jira-key.yaml
index a233cda..aa68dd4 100644
--- a/.github/workflows/check-jira-key.yaml
+++ b/.github/workflows/check-jira-key.yaml
@@ -1,6 +1,3 @@
-# Roll out to each in-scope IABTechLab uid2* repo as .github/workflows/check-jira-key.yaml
-# once uid2-shared-actions #254 is merged AND a release has moved the v3 tag to include
-# actions/check_jira_key. Non-blocking until the terraform required_status_checks rule is flipped on.
 name: Check Jira Key
 on:
   pull_request:
@@ -11,8 +8,8 @@ permissions:
   pull-requests: read
 
 jobs:
-  # Job name PINNED to `check_jira_key` so every repo produces the same status-check context
-  # ("check_jira_key") — one terraform required_status_checks entry matches all repos (UID2-7426).
+  # Job name pinned to `check_jira_key` so every gated repo yields the same status-check context
+  # for a single terraform required_status_checks entry (UID2-7426).
   check_jira_key:
     runs-on: ubuntu-latest
     steps: