Yicong-Huang commented on code in PR #5419:
URL: https://github.com/apache/texera/pull/5419#discussion_r3368632959


##########
.github/workflows/stale.yml:
##########
@@ -0,0 +1,73 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# Auto-close stale pull requests after a total of 90 days of inactivity
+# (60 days to mark stale, +30 days to close). Issues are not touched.
+#
+# Escape hatches (any one keeps a PR alive):
+#   - Add the `pinned` label
+#   - Attach a milestone
+#   - Keep the PR in draft state
+#   - Push a commit, comment, or address review feedback
+
+name: Close stale pull requests
+
+on:
+  schedule:
+    - cron: '0 1 * * 1'   # weekly, Monday 01:00 UTC
+  workflow_dispatch:
+
+permissions:
+  pull-requests: write
+

Review Comment:
   Adopted in cd22e9cfa — added `issues: write`. While PR-only mode 
(`days-before-issue-stale: -1`) likely makes this redundant, the search-issues 
enumeration path may still touch issues, so granting it removes a potential 403 
with no real cost.



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to