feat: integrate monorepo-wide linter into CI#8833
Open
shivanee-p wants to merge 16 commits into
Open
Conversation
Contributor
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
shivanee-p
force-pushed
the
shivaneep-linter-handwritten
branch
from
d4daf1a to
f32b729
Compare
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
1 participant
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.
This pull request centralizes the ESLint and GTS checking architecture across the entire google-cloud-node monorepo. It removes redundant package-level configurations, integrates type-aware linting rules, and adds the unified linter runner (bin/linter.mjs) to the CI pipeline in a non-blocking mode to ensure a smooth transition.