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(minifier): minify alternated one child if block #7231
• feat(minifier): minify one child if statement expression #7230 👈 (View in Graphite)
• test(minifier): fix minimize condition tests #7222 : 1 other dependent PR (#7223 )
• refactor(minifier): use map and and_then instead of let else #7178 : 1 other dependent PR (#7179 )
• main

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

CodSpeed Performance Report

Merging #7230 will not alter performance

_{Comparing 11-10-feat_minifier_minify_one_child_if_statement_expression (a1495e7) with main (c133693)}

Summary

✅ 30 untouched benchmarks

So we can assume it's a problem due to enabling a new peephole, same as #6698, #6266, as mentioned in #7231 (comment).

Merge activity

• Nov 26, 9:36 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 26, 9:37 AM EST: Graphite rebased this pull request after merging its parent, because this pull request is set to merge when ready.
• Nov 26, 9:48 AM EST: A user added this pull request to the Graphite merge queue.