You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@texera.apache.org by gi...@apache.org on 2026/09/18 16:15:28 UTC
(texera) branch gh-readonly-queue/main/pr-8574-d11878426b59967e5466ef6a927ef1a97d63b606 created (now 90e7baa6bc)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a change to branch gh-readonly-queue/main/pr-8574-d11878426b59967e5466ef6a927ef1a97d63b606
in repository https://gitbox.apache.org/repos/asf/texera.git
at 90e7baa6bc ci: include draft PRs in the stale-PR auto-close policy (#8574)
This branch includes the following new commits:
new 90e7baa6bc ci: include draft PRs in the stale-PR auto-close policy (#8574)
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(texera) 01/01: ci: include draft PRs in the stale-PR auto-close policy (#8574)
Posted by gi...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-8574-d11878426b59967e5466ef6a927ef1a97d63b606
in repository https://gitbox.apache.org/repos/asf/texera.git
commit 90e7baa6bc955ee3cdb23cf7ac7f2493e58fdb3a
Author: Matthew B. <mg...@uci.edu>
AuthorDate: Fri Sep 18 16:15:05 2026 +0000
ci: include draft PRs in the stale-PR auto-close policy (#8574)
### What changes were proposed in this PR?
- Stop exempting draft PRs from the stale workflow by setting
`exempt-draft-pr: false`, so drafts are covered by the same single
auto-close pass as ready PRs.
- Keep the existing timing and cadence unchanged: weekly run, 30 days to
mark stale, 7 more to close (37 days total).
- Drop the "keep the PR in draft state" line from the escape-hatch
comment, since draft state is no longer an exemption.
### Any related issues, documentation, discussions?
Closes: #8573
### How was this PR tested?
- CI/workflow-only change with no application code, so no unit tests
apply.
- Confirm the workflow parses: from the repo root run `python3 -c
"import yaml; yaml.safe_load(open('.github/workflows/stale.yml'))"`,
expect no error.
- Scheduled runs fire only from the default branch; a reviewer can
dry-run it from the Actions tab via "Run workflow" (workflow_dispatch)
and confirm a draft PR inactive for 30 days is marked `stale` and closed
7 days later, while `pinned` or milestoned drafts are left untouched.
### Was this PR authored or co-authored using generative AI tooling?
Co-authored with Claude Opus 4.8 in compliance with ASF
---
.github/workflows/stale.yml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index aaf26dea3e..d2191d07a7 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -15,12 +15,12 @@
# limitations under the License.
# Auto-close stale pull requests after a total of 37 days of inactivity
-# (30 days to mark stale, +7 days to close). Issues are not touched.
+# (30 days to mark stale, +7 days to close). Drafts are included on the same
+# window. 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
@@ -44,13 +44,13 @@ jobs:
days-before-issue-stale: -1
days-before-issue-close: -1
- # PRs: 30 days inactive -> stale, +7 days -> close.
+ # PRs (ready and draft): 30 days inactive -> stale, +7 days -> close.
days-before-pr-stale: 30
days-before-pr-close: 7
stale-pr-label: 'stale'
exempt-pr-labels: 'pinned'
exempt-all-pr-milestones: true
- exempt-draft-pr: true
+ exempt-draft-pr: false
remove-stale-when-updated: true
stale-pr-message: |