From 756b69267d335cde549770baee5c032001223b6d Mon Sep 17 00:00:00 2001 From: lxcxjxhx Date: Tue, 10 Nov 2026 23:05:40 +0800 Subject: [PATCH] CI: Drop the path filter that matches no directory `python-test-coverage.yml` lists `python/tests/unit/**` under both `pull_request.paths` and `push.paths`, but that directory has never existed in this repository: ```console $ ls python/tests samples $ git log --oneline --all -- python/tests/unit (no output) ``` Every Python test lives under `python/packages/*/tests/`, which the same filter already covers with `python/packages/**`. So the line cannot match anything, and it cannot be responsible for triggering the workflow either. The cost is not runtime, it is what a reader concludes: a paths list is documentation of "what this check watches", and a reader deciding whether their change will be covered reads `python/tests/unit/**` as "unit tests live there". They don't. If tests are ever moved to that location, the entry should come back as part of that move, where it can be tested. Removing two lines from one file; the workflow's behaviour is unchanged because the pattern never matched. --- .github/workflows/python-test-coverage.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/.github/workflows/python-test-coverage.yml b/.github/workflows/python-test-coverage.yml index a27dcbc3de2..ca3f9b97db7 100644 --- a/.github/workflows/python-test-coverage.yml +++ b/.github/workflows/python-test-coverage.yml @@ -5,7 +5,6 @@ on: branches: ["main", "feature*"] paths: - "python/packages/**" - - "python/tests/unit/**" - "python/scripts/workspace_poe_tasks.py" - ".github/scripts/python_check_coverage.py" - ".github/workflows/python-test-coverage.yml" @@ -13,7 +12,6 @@ on: branches: ["main"] paths: - "python/packages/**" - - "python/tests/unit/**" - "python/scripts/workspace_poe_tasks.py" - ".github/scripts/python_check_coverage.py" - ".github/workflows/python-test-coverage.yml"