cpoerschke commented on code in PR #2184:
URL: https://github.com/apache/solr/pull/2184#discussion_r1446319712


##########
.github/workflows/stale.yml:
##########
@@ -0,0 +1,39 @@
+# This workflow warns of PRs that have had no activity for a specified amount 
of time.
+#
+# For more information, see https://github.com/actions/stale
+name: Mark stale pull requests
+
+on:
+  # Run every day at 00:00 UTC
+  schedule:
+    - cron: '0 0 * * *'
+  # Or run on demand
+  workflow_dispatch:
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v9
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+
+          days-before-pr-stale: 14
+          days-before-issue-stale: -1   # we don't use issues
+          days-before-close: -1         # don't close stale PRs/issues
+          exempt-draft-pr: true         # don't mark draft PRs as stale
+          stale-pr-label: "stale"       # label to use when marking as stale
+
+          stale-pr-message: >
+            This PR has not had activity in the past 2 weeks, labeling it as 
stale.
+            Any new activity will remove the stale label. To attract more 
reviewers, tag

Review Comment:
   And wondering about pull requests with merge conflicts e.g. to suggest or 
not to suggest to try and resolve any merge conflicts. Maybe that would be a 
different kind of bot though.
   ```suggestion
               Any new activity will remove the stale label. To attract more 
reviewers, please tag
   ```



##########
.github/workflows/stale.yml:
##########
@@ -0,0 +1,39 @@
+# This workflow warns of PRs that have had no activity for a specified amount 
of time.
+#
+# For more information, see https://github.com/actions/stale
+name: Mark stale pull requests
+
+on:
+  # Run every day at 00:00 UTC
+  schedule:
+    - cron: '0 0 * * *'
+  # Or run on demand
+  workflow_dispatch:
+
+jobs:
+  stale:
+
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+
+    steps:
+      - uses: actions/stale@v9
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+
+          days-before-pr-stale: 14
+          days-before-issue-stale: -1   # we don't use issues
+          days-before-close: -1         # don't close stale PRs/issues
+          exempt-draft-pr: true         # don't mark draft PRs as stale
+          stale-pr-label: "stale"       # label to use when marking as stale
+
+          stale-pr-message: >
+            This PR has not had activity in the past 2 weeks, labeling it as 
stale.

Review Comment:
   Maybe shortening "has not had" to "had no" and use "visible" to signal that 
maybe someone looked but did not (yet) comment?
   ```suggestion
               This PR had no visible activity in the past 2 weeks, labeling it 
as stale.
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to