-
Notifications
You must be signed in to change notification settings - Fork 4k
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(stalebot): update stalebot's messaging and timeframes #2761
Conversation
This is an update inspired by the discussion in #1126, attempting to better communicate the reasoning behind the stalebot. Also, I've adjusted the closing timeframe (as opposed to the stale timeframe), because closing feels more harsh than the marking as stale, and is harder for a community member to reverse. Suggestions/changes welcome of course!
Codecov Report
@@ Coverage Diff @@
## master #2761 +/- ##
=======================================
Coverage 99.74% 99.74%
=======================================
Files 160 160
Lines 2762 2762
=======================================
Hits 2755 2755
Misses 7 7 Continue to review full report at Codecov.
|
Superb! Very much appreciate your views and input around this. Now for honorary business. @rijk You've contributed here before and you've shown care and initiative for ensuring SUIR becomes better. We appreciate this and want to enable you to do more. I've added you as a collaborator. You're now able to manage issues and PRs as well as create branches here in the main repo. Merging to master is the only reserved permission. We are very select about who we add and when, so know that we trust your abilities and your judgment as to good code. Please feel free to weigh in on any issues and PRs that you have an opinion about. You have a share of ownership and say here now. Once you accept the invite (see your email), you might want to show the Semantic Org badge publicly on your profile. To do that, navigate to the "people" page and change the "private" dropdown to "public" for your user in the table. Here's a direct link to your user in the table. /cc Please welcome @rijk to our ranks 😄 🎉 |
Thanks! 😄 It might be me though, but I haven't received an email yet.. @levithomason could you double check? |
@rijk Try now 😊 |
This is an update inspired by the discussion in #1126, attempting to better communicate the reasoning behind the stalebot.
Also, I've adjusted the closing timeframe (as opposed to the stale timeframe), because closing feels more harsh than the marking as stale, and is harder for a community member to reverse.
Suggestions/changes welcome of course!