From 91fa676c2677f6e9331f8ff225b446d0cabb8056 Mon Sep 17 00:00:00 2001 From: sudoforge Date: Sat, 3 Aug 2024 08:34:42 -0700 Subject: feat: improved lifecycle management with stale-bot This change refactors the automatic lifecycle management workflow that uses the `stale-bot` action library, such that neither issues nor pull requests will be closed. An additional label of `lifecycle/rotten` has been added to indicate issues or pull requests which have been inactive for 180 days or more. Change-Id: Ia748552c91ada43b4a762879db469132131956f0 --- .github/workflows/cron.yml | 29 ++++------------------------- 1 file changed, 4 insertions(+), 25 deletions(-) (limited to '.github/workflows/cron.yml') diff --git a/.github/workflows/cron.yml b/.github/workflows/cron.yml index 6d136a14..fb66a649 100644 --- a/.github/workflows/cron.yml +++ b/.github/workflows/cron.yml @@ -1,31 +1,10 @@ name: cron on: - workflow_dispatch: schedule: - - cron: '0 0 * * *' # every day at 00:00 + - cron: '17 3 * * *' # every day at 03:17 UTC jobs: - stale: - name: stale/issue-and-pr - runs-on: ubuntu-latest - permissions: - issues: write - pull-requests: write - steps: - - uses: actions/stale@v9 - with: - stale-issue-label: lifecycle/stale - stale-pr-label: lifecycle/stale - days-before-stale: 90 - days-before-close: 30 - stale-issue-message: | - This bot triages untriaged issues and PRs according to the following rules: - - - After 90 days of inactivity, the `lifecycle/stale` label is applied - - After 30 days of inactivity since `lifecycle/stale` was applied, the issue is closed - - To remove the stale status, you can: - - - Remove the `lifecycle/stale` label - - Comment on this issue + lifecycle: + if: github.event.schedule == '17 3 * * *' + uses: ./.github/workflows/stale-bot.yml -- cgit