-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
chore(chromatic): only run on ui-components changes
#7785
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.
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
Conversation
Signed-off-by: Aviv Keller <me@aviv.sh>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR modifies the Chromatic workflow configuration to only trigger on changes in the ui-components package, serving as a workaround for the Chromatic limit.
- Limits workflow triggers to changes within the ui-components folder.
- Updates both push and pull_request_target events with the new paths filter.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Aviv Keller <me@aviv.sh>
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #7785 +/- ##
==========================================
+ Coverage 75.34% 75.37% +0.02%
==========================================
Files 96 96
Lines 7862 7862
Branches 192 192
==========================================
+ Hits 5924 5926 +2
+ Misses 1937 1935 -2
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I can make the update as it being non-required. |
ui-components changes and merge groupsui-components changes
|
Lighthouse Results
|
This is a potential workaround for our Chromatic limit, but it requires us to make
Chromatica not-required check.