ci: add css and sass file extensions to turbo workflow triggers #3155
Conversation
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
Co-Authored-By: Connor Prussin <connor@dourolabs.xyz>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
cprussin
approved these changes
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Added CSS and Sass file extensions (
.css,.scss,.sass) to the path filters in theci-turbo-build.ymlandci-turbo-test.ymlGitHub Actions workflows. This ensures that changes to stylesheets will trigger the turbo build and test pipelines.Rationale
The workflow path filters were previously missing CSS and Sass file extensions, meaning changes to stylesheets would not trigger CI builds or tests. This could lead to undetected issues when styling changes are made.
How has this been tested?
The YAML syntax follows the existing pattern used for other file extensions in these workflows. The change itself is configuration-only and doesn't modify any executable code.
Link to Devin run: https://app.devin.ai/sessions/86076b6387b44483be97c86ebc79f4e7
Requested by: Connor Prussin (connor@dourolabs.xyz)
Reviewer Checklist