[PR #207] [MERGED] ci(stale): add daily Stale workflow to triage inactive issues/PRs #206

New issue

Closed

opened 2026-10-27 21:10:36 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-27 21:10:36 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/Comfy-PR/pull/207
Author: @snomiao
Created: 5/15/2026
Status: ✅ Merged
Merged: 5/17/2026
Merged by: @snomiao

Base: main ← Head: sno-stale

📝 Commits (1)

53164a8 ci(stale): auto-mark/close inactive issues, mark stale PRs

📊 Changes

1 file changed (+66 additions, -0 deletions)

View changed files

➕ .github/workflows/stale.yml (+66 -0)

📄 Description

Summary

Adds a daily actions/stale@v9 workflow to keep the issue tracker focused without touching active conversations.

Tuning:

Type	Stale after	Close after	Exempt labels
Issues	90d no activity	+14d	`pinned`, `security`, `help wanted`, `good first issue`
PRs	180d no activity	never auto-close	`pinned`, `security`, `work-in-progress`, `wip`

Items with a milestone are always exempt (exempt-all-milestones: true).
Capped at 30 operations per run (operations-per-run: 30) — full backlog drained over a few days, then steady state.
workflow_dispatch exposes a dry-run input so we can rehearse the next run before it touches anything.
remove-stale-when-updated: true — any new comment / push instantly removes the stale label.

Why now: There are stale issues that have had no activity for ~600+ days. Manual triage is overdue and the bot lets contributors revive anything still relevant by simply commenting.

Rollout suggestion: merge → trigger once via Actions → Stale → "Run workflow" → check dry-run to preview the first wave, then re-run without dry-run.

Test plan

After merge, run the workflow with dry-run=true and confirm the candidate set looks reasonable in the job log.
If the candidates look right, run without dry-run to mark the first batch.
Verify a stale label is applied and the stale comment is posted on a sample issue.
Comment on a stale issue → confirm the label is auto-removed on the next cron run.

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/Comfy-PR/pull/207 **Author:** [@snomiao](https://github.com/snomiao) **Created:** 5/15/2026 **Status:** ✅ Merged **Merged:** 5/17/2026 **Merged by:** [@snomiao](https://github.com/snomiao) **Base:** `main` ← **Head:** `sno-stale` --- ### 📝 Commits (1) - [`53164a8`](https://github.com/Comfy-Org/Comfy-PR/commit/53164a82cb9ca4841fe4d374cc589882a4ddc5e6) ci(stale): auto-mark/close inactive issues, mark stale PRs ### 📊 Changes **1 file changed** (+66 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/stale.yml` (+66 -0) </details> ### 📄 Description ## Summary Adds a daily [`actions/stale@v9`](https://github.com/actions/stale) workflow to keep the issue tracker focused without touching active conversations. **Tuning:** | Type | Stale after | Close after | Exempt labels | |---|---|---|---| | Issues | 90d no activity | +14d | `pinned`, `security`, `help wanted`, `good first issue` | | PRs | 180d no activity | **never auto-close** | `pinned`, `security`, `work-in-progress`, `wip` | - Items with a milestone are always exempt (`exempt-all-milestones: true`). - Capped at 30 operations per run (`operations-per-run: 30`) — full backlog drained over a few days, then steady state. - `workflow_dispatch` exposes a `dry-run` input so we can rehearse the next run before it touches anything. - `remove-stale-when-updated: true` — any new comment / push instantly removes the `stale` label. **Why now:** There are stale issues that have had no activity for ~600+ days. Manual triage is overdue and the bot lets contributors revive anything still relevant by simply commenting. **Rollout suggestion:** merge → trigger once via Actions → Stale → "Run workflow" → check `dry-run` to preview the first wave, then re-run without dry-run. ## Test plan - [ ] After merge, run the workflow with `dry-run=true` and confirm the candidate set looks reasonable in the job log. - [ ] If the candidates look right, run without `dry-run` to mark the first batch. - [ ] Verify a `stale` label is applied and the stale comment is posted on a sample issue. - [ ] Comment on a stale issue → confirm the label is auto-removed on the next cron run. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-27 21:10:36 +00:00