Skip to content
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

chore: next #4760

Draft
wants to merge 74 commits into
base: main
Choose a base branch
from
Draft

chore: next #4760

wants to merge 74 commits into from

Conversation

ematipico
Copy link
Member

Summary

Test Plan

ematipico and others added 30 commits November 27, 2024 16:13
@github-actions github-actions bot added A-CLI Area: CLI A-Core Area: core A-Project Area: project A-Linter Area: linter A-Parser Area: parser A-Formatter Area: formatter A-Tooling Area: internal tools A-LSP Area: language server protocol L-JavaScript Language: JavaScript and super languages L-CSS Language: CSS L-JSON Language: JSON and super languages A-Diagnostic Area: diagnostocis A-Changelog Area: changelog L-HTML Language: HTML L-Grit Language: GritQL labels Dec 19, 2024
Copy link

codspeed-hq bot commented Dec 19, 2024

CodSpeed Performance Report

Merging #4760 will degrade performances by 6.44%

Comparing next (1907096) with main (a4db155)

Summary

❌ 1 regressions
✅ 96 untouched benchmarks

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

Benchmarks breakdown

Benchmark main next Change
js_analyzer[lint_13640784270757307929.ts] 33.5 ms 35.8 ms -6.44%

@ematipico ematipico changed the title Next chore: next Dec 19, 2024
@arendjr
Copy link
Contributor

arendjr commented Dec 19, 2024

Please take care to merge instead of squash this one, or we flatten a month of history 😉

@ematipico
Copy link
Member Author

ematipico commented Dec 19, 2024

Please take care to merge instead of squash this one, or we flatten a month of history 😉

For this one PR, we must merge it using "merge commits" (not squash), otherwise all commits gets squashed and the attribution belongs only to the person that opened the PR.

@ematipico
Copy link
Member Author

@arendjr can you block the PR to avoid accidental merges?

Copy link
Contributor

@arendjr arendjr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reminder to merge instead of squash:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Changelog Area: changelog A-CLI Area: CLI A-Core Area: core A-Diagnostic Area: diagnostocis A-Formatter Area: formatter A-Linter Area: linter A-LSP Area: language server protocol A-Parser Area: parser A-Project Area: project A-Tooling Area: internal tools L-CSS Language: CSS L-Grit Language: GritQL L-HTML Language: HTML L-JavaScript Language: JavaScript and super languages L-JSON Language: JSON and super languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants