aws-actions/'Stale Issue Cleanup' Action for GitHub Actions

Close issues and pull requests with no recent activity

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Maintainedlast commit Jan 7, 2026
License
Apache 2.0

Pinned Snippet

workflow.ymlSHA-pinned
uses: aws-actions/stale-issue-cleanup@0604f2edf84a3a66bc0dfb4a30eb07814cbdf440 # v7.1.1

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
repo-tokenToken for the repository. Can be passed in using {{ secrets.GITHUB_TOKEN }}yes
issue-typesIssue types to process ("issues", "pull_requests", or "issues,pull_requests")issues,pull_requests
stale-issue-messageThe message to post on the issue when tagging it. If none provided, will not mark issues stale.
stale-pr-messageThe message to post on the pr when tagging it. If none provided, will not mark pull requests stale.
days-before-staleThe number of days old an issue can be before marking it stale.60
days-before-closeThe number of days to wait to close an issue or pull request after it being marked stale.7
stale-issue-labelThe label to apply when an issue is stale.Stale
exempt-issue-labelsThe labels to apply when an issue is exempt from being marked stale. Separate multiple labels with commas (eg. "label1,label2")
stale-pr-labelThe label to apply when a pull request is stale.Stale
exempt-pr-labelsThe labels to apply when a pull request is exempt from being marked stale. Separate multiple labels with commas (eg. "label1,label2")
ancient-issue-messageThe message to post when an issue is very old.
ancient-pr-messageThe message to post when a pr is very old.
days-before-ancientThe number of days old an issue can be before marking it ancient.360
response-requested-labelThe label that gets applied when a response is requested.
closed-for-staleness-labelThe label that gets applied when an issue is closed for staleness.
minimum-upvotes-to-exemptThe minimum number of "upvotes" that an issue needs to have before not marking as ancient.
loglevelSet to DEBUG to enable debug logging
dry-runSet to true to not perform repository changes
use-created-date-for-ancientSet to true to use issue created date instead of modified date for determining an ancient issue.

no outputs