From 8a0f38ac2aef246c183fcad3f17a895addda111c Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Thu, 5 Nov 2020 11:23:05 +0100 Subject: [PATCH] Auto expire issues and PRs Without this patch, we might hold old issues and PR for a long time. Instead we should close them. People can reopen if necessary. This would show that we have a proper triage process, and a proper way to handle those. --- .github/workflows/stale.yaml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .github/workflows/stale.yaml diff --git a/.github/workflows/stale.yaml b/.github/workflows/stale.yaml new file mode 100644 index 0000000..b3e28ac --- /dev/null +++ b/.github/workflows/stale.yaml @@ -0,0 +1,20 @@ +name: Mark stale issues and pull requests + +on: + schedule: + - cron: "30 1 * * *" + +jobs: + stale: + runs-on: ubuntu-latest + steps: + # Stale by default waits for 60 days before marking PR/issues as stale, and closes them after 7 days. + # Do not expire the first issues that would allow the community to grow. + - uses: actions/stale@v1 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + stale-issue-message: 'This issue was automatically considered stale due to lack of activity. Please update it and/or join our slack channels to promote it, before it automatically closes (in 7 days).' + stale-pr-message: 'This PR was automatically considered stale due to lack of activity. Please refresh it and/or join our slack channels to highlight it, before it automatically closes (in 7 days).' + stale-issue-label: 'no-issue-activity' + stale-pr-label: 'no-pr-activity' + exempt-issue-labels: 'good-first-issue'