Optimize CI pipeline avoiding running jobs for unrelated changes #478
Labels
🤖 aspect: dx
Concerns developers' experience with the codebase
🧰 goal: internal improvement
Improvement that benefits maintainers, not users
help wanted
Open to participation from the community
🟨 priority: medium
Not blocking but should be addressed soon
🧱 stack: frontend
Related to the Nuxt frontend
Milestone
Problem
When ones submit a change to the GH actions without altering actual Nuxt code the full CI workflow runs, that includes tasks like creating a preview for Storybook and Tailwind, checking types, and what takes longer, the Playwright tests (E2E, visual regression). For more, many of these works are flaky, it would be much better to prevent them from running early, save CPU time, and speed up the time a PR is ready for review and merge.
Description
I see two options to resolve this:
ci
workflow into separate ones and use thepath
config to filter executions by folders being modified orAlternatives
Additional context
The text was updated successfully, but these errors were encountered: