chore: Move linting rules to root level#10116
Merged
Merged
Conversation
Contributor
Author
|
I'm not actually sure if this should be a |
gonfunko
approved these changes
Jul 9, 2026
gonfunko
left a comment
gonfunko
left a comment
Contributor
There was a problem hiding this comment.
This is great, thanks! I'd probably use chore for the PR title, but up to you.
lizschwab
changed the title
github-actions
Bot
added
PR: chore
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The basics
The details
Resolves
Fixes #7760
Proposed Changes
Move eslint rules from package-level
eslint.config.mjsfiles to root-levelReason for Changes
This sets us up for moving plugins from blockly-samples over to the blockly monorepo
Test Coverage
No unit tests. I tested my changes locally by intentionally adding linting errors to each of the two projects (core and docs) and made sure it raised errors on those changes and only those changes.
