Project management: Remove automation that checks-in ANY issue without activity in 180 days #53390
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
priethor
added
the
[Type] Project Management
priethor
changed the title
tellthemachines
approved these changes
Aug 8, 2023
Contributor
tellthemachines
left a comment
tellthemachines
left a comment
There was a problem hiding this comment.
Thanks for fixing this! Change LGTM.
Contributor
Author
|
As a follow-up to this change, I've removed the now obsolete |
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.
What?
Reverts part of #29321, which introduced a check-in to every issue after 180 days without activity, so that check-ins are only performed in issues with the `Needs more info" label.
Why?
Many open issues need longer than 180 days to move forward. They might see less activity for longer periods of time just by the nature of the project and all the different priorities open in parallel. Checking in makes sense for issues labeled as
Needs more info, but can become very noisy for issues that need to be open for longer periods of time, like overview issues.#52173 tried using a different label than "Needs testing", which caused even more automation to trigger later, but it still seems too much.
How?
By removing the GitHub workflow automation that performs the 180-day check-in to all issues.