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.

• refactor(linter): rename is_same_reference to is_same_expression #7654 👈 (View in Graphite)
• main

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

CodSpeed Performance Report

Merging #7654 will not alter performance

_{Comparing c/12-04-refactor_linter_rename_is_same_reference_to_is_same_expression_ (3711a8e) with main (2179b93)}

Summary

✅ 29 untouched benchmarks

Can this be replaced by ContentEqual?

Edit: I replaced it with left.content_eq(right) but a bunch of tests failed. May need to replace it case by case :-(

Merge activity

• Dec 4, 11:07 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 4, 11:07 PM EST: A user added this pull request to the Graphite merge queue.
• Dec 4, 11:22 PM EST: A user merged this pull request with the Graphite merge queue.

Can this be replaced by ContentEqual?

Edit: I replaced it with left.content_eq(right) but a bunch of tests failed. May need to replace it case by case :-(

yeah this one is a little looser than content_eq