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

add config for probot-stale integration #2829

Merged
merged 1 commit into from
May 24, 2017
Merged

add config for probot-stale integration #2829

merged 1 commit into from
May 24, 2017

Conversation

boneskull
Copy link
Contributor

closes #2828.

Issues and PRs will be marked stale after 4 mos. of inactivity and closed if there's no activity after 2 more weeks.

Most issues with labels are exempt from the check. I'm not sure how well this is going to work, but we can always change it later.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 88.288% when pulling 468f791 on stale into fc35691 on master.

@dasilvacontin
Copy link
Contributor

I'm finding it hard to understand which issues are worthy of being marked as stale and being closed.

I can come up with:

  • help issues that ask for help with a concrete code example, we reply to them, and we never hear back from OP.

Any others?

@boneskull
Copy link
Contributor Author

@dasilvacontin IMO, we should mark the following as stale:

  • PRs that need work and have become rotten
  • Stuff marked needs-feedback that never got feedback
  • Unlabeled stuff without activity

4 mos is a long time, and there's a warning, so a user can reply and say "yes, this is still a question/problem/etc".

In the config, we're blacklisting almost every label except a few (duplicate, needs-feedback, pr-needs-work). Really, we need a whitelist instead (see probot/stale#22).

@boneskull boneskull merged commit eee62be into master May 24, 2017
@boneskull boneskull deleted the stale branch May 24, 2017 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

configure probot-stale
3 participants