node package manager

probot-stale

Probot: Stale

a GitHub Integration built with Probot that closes abandoned issues after a period of inactivity.

Inspired by @parkr's auto-reply bot that runs @jekyllbot.

Usage

  1. Configure the GitHub Integration
  2. Create .github/stale.yml

Configuration in .github/stale.yml can override these defaults:

# Number of days of inactivity before an issue becomes stale
daysUntilStale: 60
# Number of days of inactivity before a stale issue is closed
daysUntilClose: 7
# Issues with these labels will never be considered stale
exemptLabels:
  - pinned
  - security
# Label to use when marking an issue as stale
staleLabel: wontfix
# Comment to post when marking an issue as stale. Set to `false` to disable
markComment: >
  This issue has been automatically marked as stale because it has not had
  recent activity. It will be closed if no further activity occurs. Thank you
  for your contributions.
# Comment to post when closing a stale issue. Set to `false` to disable
closeComment: false

Deploying to Heroku

  1. Deploy - Click this button and pick an App Name that Heroku is happy with. Before you can complete this, you'll need config variables from the next step.
  2. In another tab, create an integration on GitHub, using https://[yourappname].herokuapp.com/ (replacing [yourappname] with the name from step 1) as the Callback URL and Webhook URL, and under Permissions & events, set:
    • Issues - Read & Write
      • Check the box for Issue comment events
      • Check the box for Issues events
  3. After creating your GitHub integration, go back to the Heroku tab and fill in the configuration variables with the values for the GitHub Integration
  4. Create a .github/ISSUE_REPLY_TEMPLATE.md file in your repository.