Update "Close inactive issues" workflow to close issues after 180 days of inactivity #909
Conversation
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
IrynaKulakova
approved these changes
Aug 18, 2025
There was a problem hiding this comment.
Pull Request Overview
Updates the GitHub workflow to close issues after 180 days of inactivity instead of the previous 70 days (60 days to mark as stale + 10 days before closing).
- Increases the stale period from 60 to 170 days, maintaining the 10-day closing period for a total of 180 days
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.
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.
We should only close issues if they have been inactive for 180 days. With this PR, we mark an issue as stale and warn the user after 60 days of inactivity, and close the issue after another 120 days if still inactive.