-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: add .github/replies.yml #5618
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
chore: add .github/replies.yml #5618
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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
My saved replies right now: Extension Rule - Reject Due to EnhancementI use this when someone requests an enhancement to an extension rule that would add or change the behaviour and cause us to break from the base rule.
Fix has been mergedI rarely use this now a days, but in the past I used this when people annoyingly asked "when will this be released?" on closed issues.
"Progress"I use this when someone obnoxiously comments on a thread ("any updates?", "+1", etc). It's intentionally kinda strongly worded and more verbose.
"Progress - Nice"I use this whenever someone is more polite in asking for updates. It's sadly used less than the other one.
Review QueueI used this when someone tags me
Use prettierI use this when someone asks for a pure formatting rule. I think I've only used this once or twice.
|
Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5618 +/- ##
==========================================
- Coverage 93.80% 91.63% -2.18%
==========================================
Files 292 134 -158
Lines 10009 1506 -8503
Branches 3010 226 -2784
==========================================
- Hits 9389 1380 -8009
+ Misses 338 62 -276
+ Partials 282 64 -218
Flags with carried forward coverage won't be shown. Click here to find out more. |
PR Checklist
Overview
Adds a first auto-reply based on #5538 (comment).