Skip to content

fix: Set use-baseline to 'warn' in recommended config #110

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 9, 2025
Merged

Conversation

nzakas
Copy link
Member

@nzakas nzakas commented Apr 9, 2025

Prerequisites checklist

What is the purpose of this pull request?

Sets the use-baseline rule to "warn" in the recommended config.

Related Issues

fixes #80

Is there anything you'd like reviewers to focus on?

@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Apr 9, 2025
@eslint-github-bot eslint-github-bot bot added the bug Something isn't working label Apr 9, 2025
Copy link
Member

@mdjermanovic mdjermanovic left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@mdjermanovic mdjermanovic merged commit 2152e9d into main Apr 9, 2025
22 checks passed
@mdjermanovic mdjermanovic deleted the issue80 branch April 9, 2025 18:18
@github-project-automation github-project-automation bot moved this from Needs Triage to Complete in Triage Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Complete
Development

Successfully merging this pull request may close these issues.

Rule Change: require-baseline might need to default to a warning
2 participants