Skip to content

ci: move the stale PR workflow where GitHub runs it - #2475

Merged
milenkovicm merged 1 commit into
apache:mainfrom
NoahKusaba:ci/enable-stale-workflow
Sep 23, 2026
Merged

milenkovicm merged 1 commit into
apache:mainfrom
NoahKusaba:ci/enable-stale-workflow

Conversation

@NoahKusaba

Copy link
Copy Markdown
Contributor

Rationale for this change

stale.yml was committed to the repository root in #1488. GitHub only looks for workflows in .github/workflows/, so it has never run.

What changes are included in this PR?

  • Move it to .github/workflows/stale.yml.
  • Move permissions to the top level, and add workflow_dispatch and a timeout-minutes.

Behaviour is unchanged from what #1488 intended: it runs nightly, marks PRs with no activity for 60 days as stale, and closes them 7 days later. Issues are left alone. Drafts are not exempt.

Are there any user-facing changes?

Yes, for contributors, and this needs an explicit yes from a maintainer. Because the workflow has never run, its first nightly run sweeps the whole backlog. As of 2026-09-13, 8 of the 45 open PRs had no activity for 60 days, including 3 drafts. They would be marked stale and closed 7 days later unless someone comments.

If that's not wanted, alternatives are exempting drafts (exempt-draft-pr: true), a longer window, or deleting stale.yml instead.

Split out of #2438 to make it easier to review.

🤖 Generated with Claude Code

stale.yml was committed to the repository root in apache#1488, where GitHub does not
look for workflows, so it has never run. Move it to .github/workflows/ and
enable it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@milenkovicm
milenkovicm merged commit 635eb8e into apache:main Sep 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants