From 7cef07dfa991156f2258af18f2f565575e918e05 Mon Sep 17 00:00:00 2001 From: James Lamb Date: Tue, 2 Jan 2024 22:14:25 -0600 Subject: [PATCH] [ci] update issue-locking workflow --- .github/workflows/lock.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index 72d8b7c2f585..4efe658b7f45 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -18,15 +18,15 @@ jobs: action: runs-on: ubuntu-latest steps: - - uses: dessant/lock-threads@v4 + - uses: dessant/lock-threads@v5 with: github-token: ${{ github.token }} # after how many days of inactivity should a closed issue/PR be locked? - issue-inactive-days: '90' - pr-inactive-days: '90' + issue-inactive-days: '365' + pr-inactive-days: '365' # do not close feature request issues... # we close those but track them in https://github.com/microsoft/LightGBM/issues/2302 - exclude-any-issue-labels: '"feature request"' + exclude-any-issue-labels: 'feature request' # what labels should be removed prior to locking? remove-issue-labels: 'awaiting response,awaiting review,blocking,in progress' remove-pr-labels: 'awaiting response,awaiting review,blocking,in progress' @@ -42,3 +42,4 @@ jobs: # what shoulld the locking status be? issue-lock-reason: 'resolved' pr-lock-reason: 'resolved' + process-only: 'issues, prs'