Skip to content
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

Merged
merged 1 commit into from
May 3, 2018
Merged

Conversation

rijk
Copy link
Member

@rijk rijk commented May 3, 2018

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!

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-io
Copy link

Codecov Report

Merging #2761 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93f4b9c...44fe56a. Read the comment docs.

@layershifter layershifter changed the title Update stalebot's messaging and timeframes chore(stalebot): update stalebot's messaging and timeframes May 3, 2018
@levithomason
Copy link
Member

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
@Semantic-Org/react-collaborators
@Semantic-Org/react-maintainers

Please welcome @rijk to our ranks 😄 🎉

@levithomason levithomason merged commit 4b96bef into Semantic-Org:master May 3, 2018
@rijk rijk deleted the patch-1 branch May 4, 2018 07:47
@rijk
Copy link
Member Author

rijk commented May 4, 2018

Thanks! 😄

It might be me though, but I haven't received an email yet.. @levithomason could you double check?

@levithomason
Copy link
Member

@rijk Try now 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants