Skip to content

Automatically Manage Stale Issues and PRs #3818

@jerop

Description

@jerop

Summary

To maintain a clean and relevant backlog, we need an automated way to identify and close issues and pull requests that have been inactive for an extended period. This workflow will prevent stale items from cluttering our project board and ensure that contributors and maintainers are focused on active work. It also gently nudges contributors for follow-up before closing their items.

Acceptance Criteria

  • When an issue or PR has no activity for 60 days, it is automatically labeled as stale.
  • A comment is posted on the item explaining that it has been marked as stale due to inactivity and will be closed if no further activity occurs.
  • If an item labeled stale receives any updates (new comments, commits, etc.), the stale label is automatically removed.
  • If an item remains stale for an additional 14 days with no activity, it is automatically closed.
  • A final comment is posted explaining why the item was closed.
  • Items with specific labels like pinned or security are exempt from this process.

Implementation Notes

  • Use the official actions/stale GitHub Action.
  • Create a new workflow file at .github/workflows/stale.yml.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/contributionImproves the contribution process via test automation and CI/CD pipeline enhancements.kind/enhancementNew feature or requestmaintainerFor Roadmap Itemspriority/p2Important but can be addressed in a future release.

    Type

    Projects

    Status

    No status

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions