docs(website): pruning flow for issues and PRs #6002
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 settings. |
| @@ -1,4 +1,7 @@ | |||
| replies: | |||
| - body: | | |||
| 👋 Hey @{{ author }}! Just checking in, is this still something you have time for? No worries if not - I just don't want to leave it hanging. | |||
There was a problem hiding this comment.
This just reminded me of JoshuaKGoldberg/refined-saved-replies#45...
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #6002 +/- ##
==========================================
- Coverage 91.42% 91.29% -0.14%
==========================================
Files 365 365
Lines 12339 12343 +4
Branches 3609 3610 +1
==========================================
- Hits 11281 11268 -13
- Misses 753 767 +14
- Partials 305 308 +3
Flags with carried forward coverage won't be shown. Click here to find out more.
|
PR Checklist
Overview
Describes how we close old issues & PRs. And by "we" I mean how I have been doing it 😄 - would be nice to see if there's a better way!