This is an automated email from the ASF dual-hosted git repository.

monkeydluffy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix.git


The following commit(s) were added to refs/heads/master by this push:
     new f2864c307 chore(ci): automate management of unresponded issues (#9927)
f2864c307 is described below

commit f2864c30723acb9820e659a1aae163c46892b1f9
Author: Abhishek Choudhary <[email protected]>
AuthorDate: Tue Aug 8 07:58:47 2023 +0545

    chore(ci): automate management of unresponded issues (#9927)
---
 .github/workflows/close-unresponded.yml | 38 +++++++++++++++++++++++++++++++++
 .github/workflows/update-labels.yml     | 19 +++++++++++++++++
 2 files changed, 57 insertions(+)

diff --git a/.github/workflows/close-unresponded.yml 
b/.github/workflows/close-unresponded.yml
new file mode 100644
index 000000000..52e81228e
--- /dev/null
+++ b/.github/workflows/close-unresponded.yml
@@ -0,0 +1,38 @@
+name: Check Issues
+
+on:
+  workflow_dispatch:
+  schedule:
+  - cron: '0 10 * * *'
+
+permissions:
+  contents: read
+
+jobs:
+  prune_stale:
+    permissions:
+      issues: write  # for actions/stale to close stale issues
+    name: Prune Unresponded
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+
+    steps:
+    - name: Prune Stale
+      uses: actions/stale@v8
+      with:
+        days-before-issue-stale: 14
+        days-before-issue-close: 3
+        stale-issue-message: >
+          Due to lack of the reporter's response this issue has been labeled 
with "no response".
+          It will be close in 3 days if no further activity occurs. If this 
issue is still
+          relevant, please simply write any comment. Even if closed, you can 
still revive the
+          issue at any time or discuss it on the [email protected] list.
+          Thank you for your contributions.
+        close-issue-message: >
+          This issue has been closed due to lack of activity. If you think that
+          is incorrect, or the issue requires additional review, you can 
revive the issue at
+          any time.
+        # Issues with these labels will never be considered stale.
+        only-labels: 'wait for update'
+        stale-issue-label: 'no response'
+        ascending: true
diff --git a/.github/workflows/update-labels.yml 
b/.github/workflows/update-labels.yml
new file mode 100644
index 000000000..9667dfda6
--- /dev/null
+++ b/.github/workflows/update-labels.yml
@@ -0,0 +1,19 @@
+name: Update label when user responds
+permissions:
+  issues: write
+
+on:
+  issue_comment:
+    types: [created]
+
+jobs:
+  run-check:
+    if: ${{ !github.event.issue.pull_request }} # don't execute for PR comments
+    runs-on: ubuntu-latest
+    steps:
+      - name: update labels when user responds
+        uses: andymckay/labeler@master
+        if: ${{ github.event.comment.user.login == 
github.event.issue.user.login && contains(github.event.issue.labels.*.name, 
'wait for update') && !contains(github.event.issue.labels.*.name, 'user 
responded') }}
+        with:
+          add-labels: 'user responded'
+          remove-labels: 'wait for update'

Reply via email to