Repository navigation
Remove the stale workflow that never runs - #161
Merged
Merged
Conversation
The job targets ubuntu-20.04, a GitHub-hosted image that has been retired, so no runner ever picks it up and GitHub cancels it after 24 hours in the queue. None of the runs still on record succeeded, yet each one shows up in the ASF GitHub Actions usage report as a full day of runner time. Updating the runner is not worthwhile. Issues are disabled on this repository, the pending-response label the issue rules filter on does not exist, and the repository sees too few pull requests to need automated closing.
potiuk
approved these changes
Nov 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
Close stale PRs & Issuesworkflow has not worked for a long time. It targetsubuntu-20.04, a GitHub-hosted image that has been retired, so no runner picks the job up and it stays queued until GitHub cancels it after 24 hours. All 403 finished runs still on record, going back to 2025-09-29, were cancelled that way.The job never runs, so it should not cost any compute. It does show up in the ASF GitHub Actions usage report, though: 14 runs at
1d 0heach, for 20.2k SRS-min. That matches 14 x 1440 minutes, so the report appears to count queue time as runtime.Removing it is better than moving it to a supported runner, because little of it would still apply:
pending-responselabel that the issue rules filter on does not exist.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5.5) following the guidelines
🤖 Generated with Claude Code