chore: enable codecov comment to see changes#20719
Conversation
|
|
This PR is packaged and the instant preview is available (5e7dc11). Install it locally:
npm i -D webpack@https://pkg.pr.new/webpack@5e7dc11
yarn add -D webpack@https://pkg.pr.new/webpack@5e7dc11
pnpm add -D webpack@https://pkg.pr.new/webpack@5e7dc11 |
There was a problem hiding this comment.
Pull request overview
This PR updates the repository’s Codecov configuration to allow Codecov to post PR comments showing coverage changes/diffs again.
Changes:
- Removes the
comment: offsetting fromcodecov.yml, re-enabling Codecov PR comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #20719 +/- ##
=======================================
Coverage 91.42% 91.42%
=======================================
Files 559 559
Lines 55091 55091
Branches 14528 14528
=======================================
Hits 50368 50368
Misses 4723 4723
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Merging this PR will improve performance by 41.15%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ⚡ | Memory | benchmark "many-modules-commonjs", scenario '{"name":"mode-production","mode":"production"}' |
10.1 MB | 7.2 MB | +41.15% |
| ⚡ | Memory | benchmark "many-modules-esm", scenario '{"name":"mode-production","mode":"production"}' |
11.1 MB | 8.6 MB | +29.08% |
Comparing chore-enable-codecov-comment (65fb0f4) with main (807a88e)
Summary
chore - enable comment to see coverage diff
What kind of change does this PR introduce?
chore
Did you add tests for your changes?
Existing
Does this PR introduce a breaking change?
No
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Nothing
Use of AI
No