-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: emphasize typescript-eslint in Packages page #8419
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
docs: emphasize typescript-eslint in Packages page #8419
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8419 +/- ##
==========================================
- Coverage 87.74% 86.94% -0.81%
==========================================
Files 398 252 -146
Lines 13827 12251 -1576
Branches 4067 3861 -206
==========================================
- Hits 12133 10652 -1481
+ Misses 1397 1332 -65
+ Partials 297 267 -30
Flags with carried forward coverage won't be shown. Click here to find out more. |
Co-authored-by: Brad Zacher <brad.zacher@gmail.com>
PR Checklist
Overview
This is what I was thinking: to direct people to think of
typescript-eslint
as the main one. And also emphasize the value of the Getting Started page.