Skip to content

Conversation

@Rozerinay
Copy link
Contributor

No description provided.

@Rozerinay Rozerinay requested review from a team as code owners February 2, 2026 15:42
@Rozerinay Rozerinay added the do not merge Pull requests that should not be merged just yet label Feb 2, 2026
@vercel
Copy link

vercel bot commented Feb 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
themes Ready Ready Preview, Comment Feb 2, 2026 3:46pm

Request Review

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 2, 2026

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.51%. Comparing base (30bb360) to head (ff7260a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1340   +/-   ##
=======================================
  Coverage   89.51%   89.51%           
=======================================
  Files          19       19           
  Lines        1392     1392           
  Branches      185      174   -11     
=======================================
  Hits         1246     1246           
+ Misses        146      145    -1     
- Partials        0        1    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Pull requests that should not be merged just yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants