From b558bc7de6aec5dcd63bbb832d96f98e0cf96e2a Mon Sep 17 00:00:00 2001 From: Daniel Han Date: Sun, 5 Jul 2026 23:20:05 +0000 Subject: [PATCH] ci(studio-backend): trigger on docker/** so the JupyterLab feature validation guards docker-only changes The 'Docker JupyterLab/notebook feature validation' step runs tests/validate_studio_features.py, which checks docker/jupyter (the labextension, overrides.json, login branding) and the docker notebook helpers. The pull_request paths filter listed studio/unsloth/tests but not docker/**, so a PR that only touches docker/ would skip that step and a regression in those files could pass CI. Add docker/** so the validation runs whenever the files it checks change. --- .github/workflows/studio-backend-ci.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/studio-backend-ci.yml b/.github/workflows/studio-backend-ci.yml index c0abd78d74..b3392e7d07 100644 --- a/.github/workflows/studio-backend-ci.yml +++ b/.github/workflows/studio-backend-ci.yml @@ -30,6 +30,11 @@ on: - 'unsloth/**' - 'unsloth_cli/**' - 'tests/**' + # The "Docker JupyterLab/notebook feature validation" step below runs + # tests/validate_studio_features.py, which checks docker/jupyter (the + # labextension, overrides.json, login branding) and the docker notebook + # helpers. Without docker/** here a docker-only change skips that guard. + - 'docker/**' - 'pyproject.toml' - '.github/workflows/studio-backend-ci.yml' push: