Skip to content

fix(linter): false positive in import/no-empty-named-blocks#9974

Merged
graphite-app[bot] merged 1 commit intomainfrom
03-23-fix/import-no-empty-named-blocks
Mar 23, 2025
Merged

fix(linter): false positive in import/no-empty-named-blocks#9974
graphite-app[bot] merged 1 commit intomainfrom
03-23-fix/import-no-empty-named-blocks

Conversation

@shulaoda
Copy link
Contributor

closes #9914

@shulaoda shulaoda requested review from Sysix, camc314 and camchenry March 22, 2025 17:25
@graphite-app
Copy link
Contributor

graphite-app bot commented Mar 22, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added A-linter Area - Linter C-bug Category - Bug labels Mar 22, 2025
@shulaoda shulaoda force-pushed the 03-23-fix/import-no-empty-named-blocks branch from 8ffe74e to 9c32b4f Compare March 22, 2025 17:27
@codspeed-hq
Copy link

codspeed-hq bot commented Mar 22, 2025

CodSpeed Instrumentation Performance Report

Merging #9974 will not alter performance

Comparing 03-23-fix/import-no-empty-named-blocks (6c4b533) with main (402d8b7)

Summary

✅ 33 untouched benchmarks

@Sysix Sysix added the 0-merge Merge with Graphite Merge Queue label Mar 23, 2025
Copy link
Member

Sysix commented Mar 23, 2025

Merge activity

  • Mar 22, 9:24 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
  • Mar 22, 9:24 PM EDT: A user added this pull request to the Graphite merge queue.
  • Mar 22, 9:29 PM EDT: A user merged this pull request with the Graphite merge queue.

@graphite-app graphite-app bot force-pushed the 03-23-fix/import-no-empty-named-blocks branch from 71205a8 to 6c4b533 Compare March 23, 2025 01:24
@graphite-app graphite-app bot merged commit 6c4b533 into main Mar 23, 2025
25 checks passed
@graphite-app graphite-app bot deleted the 03-23-fix/import-no-empty-named-blocks branch March 23, 2025 01:29
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter C-bug Category - Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Panic byte index 13 is not a char boundary in no_empty_named_blocks rule

3 participants