Issues
So you've got a bug report, documentation request, or feature suggestion? Great!
Please do:
- Make sure you're using the latest version of our packages
- Search all opened and closed issues to make sure your issue wouldn't be a duplicate
- Fill out the appropriate issue template completely
- Provide as much information as you can
Commenting
Please do comment on any open issue if you have more information that would be useful.
Please don't:
- Leave useless comments such as "+1" or "when's this getting fixed?" that only act as spam
- If you have nothing to add but enthusiasm and joy, add a reaction such as 👍
- One exception: if an issue has been blocked on a question to a maintainer for 3 or more months, please ping us - we probably lost track of it
- Bring up unrelated topics in existing issues: instead, file a new issue
- Comment on closed PRs: instead, file a new issue
- Comment on commits directly, as those comments are not searchable: instead, file a new issue
Issue Claiming
We don't use any kind of issue claiming system. We've found in the past that they result in accidental "licked cookie" situations where contributors claim an issue but run out of time or energy trying before sending a PR.
If an issue has been marked as accepting prs
and an open PR does not exist, feel free to send a PR.
You don't need to ask for permission.
Questions and Support Requests
The issue tracker is not an appropriate place for questions or support requests. You can instead:
- Ask in our Discord server's
#help
server - Ask a question on StackOverflow using the
typescript-eslint
tag - Publicly toot @tseslint on Mastodon or tweet @tseslint on Twitter
Note that requests to add documentation are allowed, even encouraged! 📝
Thanks for reading through this file in full! Please include your favorite emoji at the bottom of your issue to hint to us that you did in fact read this file. 💖 is a good starter if you're not sure which to use.