Skip to content

ci: optimise CI workflows with path filters and split tests #881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
GaryJones merged 2 commits into from
Jan 8, 2026
Merged

ci: optimise CI workflows with path filters and split tests #881

GaryJones merged 2 commits into from
Jan 8, 2026

Conversation

@GaryJones
Copy link
Contributor

@GaryJones GaryJones commented Jan 8, 2026

Summary

  • Add path filters to all CI workflows to skip tests for irrelevant changes (e.g., docs-only PRs)
  • Split E2E and JS tests into separate workflows for faster feedback

Changes

Path Filters

All workflows now only run when relevant files change:

  • integration.yml: PHP files, composer files, phpunit config
  • php-lint.yml: PHP files, composer files, PHPCS config
  • e2e-tests.yml: JS/CSS files, package files, webpack config, E2E tests
  • js-tests.yml: JS/TS files, package files, Jest config

Workflow Split

The previous e2e-and-js-tests.yml has been split into:

  • js-tests.yml: Runs ESLint and Jest unit tests (fast, no wp-env needed)
  • e2e-tests.yml: Runs E2E tests with Playwright (requires wp-env)

This provides faster feedback for pure JS changes since Jest doesn't need the full WordPress environment.

Test plan

  • Verify docs-only changes don't trigger test workflows
  • Verify JS-only changes trigger js-tests.yml but not integration.yml
  • Verify PHP-only changes trigger php-lint.yml and integration.yml but not js-tests.yml

🤖 Generated with Claude Code

GaryJones and others added 2 commits January 7, 2026 16:55
@GaryJones
ci: add path filters to skip tests for irrelevant changes
efb3f95
@GaryJones @claude
ci: split JS tests and E2E tests into separate workflows
5aa5ac5 
Jest unit tests don't need wp-env, so separating them provides faster
feedback for pure JS changes. E2E tests still require the full
WordPress environment with Playwright.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@GaryJones GaryJones requested a review from a team as a code owner January 8, 2026 12:46
@GaryJones GaryJones self-assigned this Jan 8, 2026
@GaryJones GaryJones added the type: maintenance Routine maintenance and code quality improvements label Jan 8, 2026
@GaryJones GaryJones added this to the Next milestone Jan 8, 2026
@GaryJones GaryJones merged commit 1d04754 into develop Jan 8, 2026
16 checks passed
@GaryJones GaryJones deleted the ci/add-path-filters branch January 8, 2026 12:58
@GaryJones GaryJones mentioned this pull request Jan 12, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@GaryJones GaryJones

Labels

type: maintenance Routine maintenance and code quality improvements

Projects

None yet

Milestone

0.10.3

Development

Successfully merging this pull request may close these issues.

2 participants

@GaryJones