Skip to content

test: probe the paths filter of ci.yml (do not merge) - #127

Closed
zy1233 wants to merge 2 commits into
refactor/move-vscode-to-rootfrom
test/ci-filter-probe
Closed

zy1233 wants to merge 2 commits into
refactor/move-vscode-to-rootfrom
test/ci-filter-probe

Conversation

@zy1233

@zy1233 zy1233 commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Throwaway probe. Do not merge. I close it after the check.

Question: does the paths filter of ci.yml (PR #126) skip Ruff and pytest on GitHub for a change that touches only the excluded files, and does a .py file inside vscode/ bring them back?

  • Step 1 (this commit): vscode/PACKAGING.md, one docs/ file and .github/workflows/vscode-extension.yml, one line each. Expected: vscode-extension.yml runs, CI does not.
  • Step 2 (next commit): one docstring line in vscode/scripts/python_licenses.py. Expected: CI runs.

@zy1233

zy1233 commented Nov 13, 2026

Copy link
Copy Markdown
Owner Author

Result of the probe, on GitHub:

  • Step 1 (commit 2525df9): only vscode/PACKAGING.md, one docs/ file and .github/workflows/vscode-extension.yml. Only VS Code extension started. CI (Ruff, pytest) did not start.
  • Step 2 (commit d88872b): the same, and one docstring line in vscode/scripts/python_licenses.py. CI started (run 43356296703).

So the paths filter of #126 works in both directions. I cancel the runs and close this pull request. Not merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant