Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

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

• feat(linter): report identical logical expressions in const-comparisons #7630
• feat(linter): enhance const-comparisons for more cases #7628 👈 (View in Graphite)
• refactor(linter): use get_inner_expression in const-comparisons #7627
• main

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

CodSpeed Performance Report

Merging #7628 will not alter performance

_{Comparing c/12-03-feat_linter_enhance_const-comparisons_for_more_cases (afe1e9b) with main (3b1e63e)}

Summary

✅ 29 untouched benchmarks

ecosystem CI: https://github.com/oxc-project/oxlint-ecosystem-ci/actions/runs/12150048897/job/33882055967
looks good - caught an issue in napi-rs

Merge activity

• Dec 3, 8:59 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 3, 9:25 PM EST: The Graphite merge queue removed this pull request due to downstack failures on PR #7627.
• Dec 3, 9:26 PM EST: A user removed this pull request from the Graphite merge queue.
• Dec 3, 9:51 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Dec 3, 9:51 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 3, 10:09 PM EST: A user merged this pull request with the Graphite merge queue.