Create a GitHub workflow that automatically marks issues as stale after 30 days of inactivity and closes them 5 days after being marked as stale.
Why are these changes being made?
This workflow is implemented to manage and clean up inactive issues in the repository, reducing clutter and helping maintain focus on active issues. By using a cron schedule and setting specific conditions, it automates the process to ensure that issues with no recent activity are reviewed and closed systematically, ensuring better resource allocation and project management.
Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description
Description by Korbit AI
What change is being made?
Create a GitHub workflow that automatically marks issues as stale after 30 days of inactivity and closes them 5 days after being marked as stale.
Why are these changes being made?
This workflow is implemented to manage and clean up inactive issues in the repository, reducing clutter and helping maintain focus on active issues. By using a cron schedule and setting specific conditions, it automates the process to ensure that issues with no recent activity are reviewed and closed systematically, ensuring better resource allocation and project management.