Skip to content

Conversation

@Boshen
Copy link
Member

@Boshen Boshen commented Nov 21, 2025

No description provided.

Copy link
Member Author

Boshen commented Nov 21, 2025


How to use the Graphite Merge Queue

Add the label merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@codecov
Copy link

codecov bot commented Nov 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.00%. Comparing base (f38eab5) to head (cfa2279).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #859   +/-   ##
=======================================
  Coverage   94.00%   94.00%           
=======================================
  Files          17       17           
  Lines        2984     2984           
=======================================
  Hits         2805     2805           
  Misses        179      179           

☔ 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.

@graphite-app
Copy link

graphite-app bot commented Nov 21, 2025

Merge activity

@graphite-app graphite-app bot force-pushed the 11-21-refactor_change_tsconfig_parse_to_accept_owned_string_add_replace_bom_with_whitespace branch from dbdcf2e to cfa2279 Compare November 21, 2025 13:42
@graphite-app graphite-app bot merged commit cfa2279 into main Nov 21, 2025
18 checks passed
@graphite-app graphite-app bot deleted the 11-21-refactor_change_tsconfig_parse_to_accept_owned_string_add_replace_bom_with_whitespace branch November 21, 2025 13:46
@Boshen Boshen mentioned this pull request Nov 21, 2025
@codspeed-hq
Copy link

codspeed-hq bot commented Nov 21, 2025

CodSpeed Performance Report

Merging #859 will degrade performances by 7.36%

Comparing 11-21-refactor_change_tsconfig_parse_to_accept_owned_string_add_replace_bom_with_whitespace (cfa2279) with main (f38eab5)1

Summary

⚡ 1 improvement
❌ 1 regression
✅ 9 untouched
⏩ 5 skipped2

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark BASE HEAD Change
resolver_memory[multi-thread] 485.3 µs 468.3 µs +3.64%
resolver_real[multi-thread] 472.6 µs 510.1 µs -7.36%

Footnotes

  1. No successful run was found on main (cfa2279) during the generation of this report, so f38eab5 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

  2. 5 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants