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: Add probot-stale #3060

Merged
merged 1 commit into from Nov 22, 2018
Merged

chore: Add probot-stale #3060

merged 1 commit into from Nov 22, 2018

Conversation

reconbot
Copy link
Contributor

PR Checklist:

  • I have run npm test locally and all tests are passing.
  • I have added/updated tests for any new behavior.
  • If this is a significant change, an issue has already been created where the problem / solution was discussed: cc @mikeal

PR Description

There are a few years of stale issues and prs. This bot will close issues over a year old and give people a chance to respond if they think the issue should stay open. After a manual review of more recent issues, we should tighten this down to 60 or 90 days.

https://probot.github.io/apps/stale/

https://probot.github.io/apps/stale/

There are a few years of stale issues and prs. This bot will close issues over a year old and give people a chance to respond if they think the issue should stay open. After a manual review of more recent issues, we should tighten this down to 60 or 90 days.
@reconbot reconbot merged commit cdca238 into master Nov 22, 2018
@reconbot reconbot deleted the reconbot/stale-issues branch November 22, 2018 05:44
@mikeal
Copy link
Member

mikeal commented Nov 22, 2018

+1, I don't see any other way to get the issue/pr list under control.

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.

None yet

2 participants