mirror of
https://github.com/Comfy-Org/github-workflows.git
synced 2026-11-05 00:17:37 +00:00
[PR #26] [MERGED] feat(stale): reusable stale-PR workflow + name the repo in the Slack digest (BE-2776) #36
Labels
No labels
cursor-review-catalog-drift
groom
groom
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/github-workflows#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Comfy-Org/github-workflows/pull/26
Author: @mattmillerai
Created: 7/9/2026
Status: ✅ Merged
Merged: 7/21/2026
Merged by: @mattmillerai
Base:
main← Head:matt/be-2776-stale-reusable📝 Commits (3)
36f24cafeat(stale): add reusable stale-PR workflow + name the repo in the Slack digest (BE-2776)a56f3a8Merge remote-tracking branch 'origin/main' into matt/be-2776-stale-reusablee75e2f2fix(stale): harden Slack digest step per review panel (BE-2776)📊 Changes
2 files changed (+219 additions, -0 deletions)
View changed files
➕
.github/workflows/stale.yml(+218 -0)📝
README.md(+1 -0)📄 Description
ELI-5
Two repos (cloud and comfy-infra) each had their own copy of the same "stale PR bot" workflow, and both post to the same Slack channel. Their digests looked identical — a bare
#158doesn't say which repo it's from, so the two batches were impossible to tell apart. This adds one shared reusable version of that workflow to this repo (so there's no more copy-paste drift), and makes the Slack header name the source repo so each batch is unambiguous.What this PR does
.github/workflows/stale.ymlas a reusable (on: workflow_call). It ports the existingactions/stale+ Slackchat.postMessagelogic verbatim, parameterizing what differs per repo:slack_channel(defaultC08V9NDB3B4),days_before_pr_stale/days_before_pr_close,stale_pr_message/close_pr_message,stale_pr_label,exempt_pr_labels, and adry_runpass-through.SLACK_BOT_TOKENis passed viasecrets:(optional — the sweep still runs without it).schedule+workflow_dispatchdry-run toggle (a reusable can't declare those triggers); the header documents the caller pattern.*Stale PR bot — <owner/repo>*) so two repos' batches in the same channel are distinguishable. Per-PR link lines are unchanged — they already resolve viagithub.repository.actionlint(+shellcheckon the inline script) is clean.Follow-ups (must land after this merges)
Per the "land the reusable first, then flip callers" sequencing (a caller referencing a not-yet-merged path fails), these are separate PRs in their own repos, pinned to this PR's merge SHA:
Comfy-Org/cloud/.github/workflows/stale.ymlwith a thin caller.Comfy-Org/comfy-infra/.github/workflows/stale.ymlwith a thin caller.bump-stale-callers.ymldispatcher (mirroringbump-cursor-review-callers.yml) to keep those callers pinned — deferred because the callers don't exist yet.stale-issues.ymlare a different issue-triage bot, out of scope).Judgment calls
exempt_pr_labelsdefault is cloud's superset (includesdo-not-merge); comfy-infra's current copy omits it. Broadening to exemptdo-not-mergeis arguably an improvement (don't nag/close a deliberately-held PR), but the comfy-infra caller can override the input to its exact prior set if desired.days_before_pr_closeinstead of a hardcoded "14"; the closed-digest line drops the "(~4 weeks inactive)" parenthetical since it was only accurate at the default 14/14 thresholds.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.