[ci] Keep required tests reporting after wiki pointer commits (#230) (#231)

* [ci] Keep required tests reporting after wiki pointer commits (#230)

* Update wiki submodule pointer for PR #231

* [changelog] Move test-check fix after release (#230)

* [ci] Cancel superseded test runs after scope detection (#230)

* [ci] Run required PR tests without path filters (#230)

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Author: coisa

.github/wiki

@@ -26,13 +26,7 @@ on:
                 type: number
                 default: -1
     pull_request:
-        paths:
-          - 'src/**'
-          - 'tests/**'
-          - 'composer.json'
-          - 'composer.lock'
-          - '.github/actions/**'
-          - '.github/workflows/tests.yml'
+        types: [opened, synchronize, reopened]
     push:
         branches: [ "main" ]
 

.github/workflows/tests.yml

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Keep required PHPUnit matrix checks reporting after workflow-managed `.github/wiki` pointer commits by running the pull-request test workflow without top-level path filters and aligning the packaged consumer test wrapper (#230)
+
 ## [1.21.0] - 2026-04-24
 
 ### Changed

CHANGELOG.md

@@ -96,6 +96,14 @@ should either allow the workflow token to update PR branches or require authors
 to refresh generated pointers manually. The preferred path is to allow bot
 updates on PR branches while keeping ``main`` protected.
 
+Required test checks must still report for workflow-managed pointer commits.
+The tests workflow therefore triggers on every pull request update without
+top-level path filters. This ensures GitHub always creates the required
+``Run Tests`` matrix checks for the latest pull request head, including bot
+commits that only refresh ``.github/wiki``. Test workflow concurrency cancels
+older in-progress runs for the same pull request so the newest commit owns the
+required check contexts.
+
 At a high level, the workflows need permission to read repository contents,
 write generated preview commits, update pull request comments, and publish Pages
 content. Keep those permissions scoped to the workflow jobs that actually need

docs/advanced/branch-protection-and-bot-commits.rst

@@ -2,6 +2,11 @@ name: "Fast Forward Test Suite"
 
 on:
   push:
+  pull_request:
+    types:
+      - opened
+      - synchronize
+      - reopened
   workflow_dispatch:
     inputs:
       max-outdated: