Skip to content

offboard from eslint in superlinter #167

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2025
Merged

offboard from eslint in superlinter #167

merged 1 commit into from
Apr 28, 2025

Conversation

bdehamer
Copy link
Collaborator

Stop running eslint as part of the super-linter action. We've been pinned to an old version of super-linter cause the newer versions are not compatible with our updated eslint config. Until super-linter has support for eslint v9 we should leave this disabled.

Adds an explicit call to eslint to make-up for disabling it in super-linter.

Signed-off-by: Brian DeHamer <bdehamer@github.com>
@Copilot Copilot AI review requested due to automatic review settings April 28, 2025 17:49
@bdehamer bdehamer requested a review from a team as a code owner April 28, 2025 17:49
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR disables ESLint within super-linter due to compatibility issues with ESLint v9 and adds an explicit ESLint step.

  • Disables ESLint in super-linter by setting VALIDATE_TYPESCRIPT_ES to false.
  • Upgrades the super-linter version reference in the workflow.
  • Introduces a new step to run ESLint via npm.

@bdehamer bdehamer requested a review from ejahnGithub April 28, 2025 17:50
@bdehamer bdehamer merged commit 32cff21 into main Apr 28, 2025
20 checks passed
@bdehamer bdehamer deleted the bdehamer/linter branch April 28, 2025 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants