ci: add path filtering to performance testing workflow#59320
Open
joshtrichards wants to merge 1 commit intomasterfrom
Open
ci: add path filtering to performance testing workflow#59320joshtrichards wants to merge 1 commit intomasterfrom
joshtrichards wants to merge 1 commit intomasterfrom
Conversation
Signed-off-by: Josh <josh.t.richards@gmail.com>
joshtrichards
requested review from
CarlSchwan,
leftybournes and
salmart-dev
and removed request for
a team
nickvergessen
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
performancetesting workflow currently runs on every pull request regardless of which files changed. Since it profiles PHP/WebDAV endpoints, it can safely be skipped when a PR only touches JS, CSS, docs, or other non-PHP files.This adds a changes job using
dorny/paths-filter(matching the pattern used across the other workflows) and gatesperformance-testingbehind it.Benefit
It's one job, so billable minutes ≈ wall-clock time: ~4–10 minutes per trigger. And less runners occupied.
TODO
Checklist
3. to review, feature component)stable32)AI (if applicable)