ci: add workflow to close stale issues #2199
Merged
Conversation
This file contains 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
maschad
requested review from
digorithm,
arboleya,
Torres-ssf,
Dhaiwat10,
danielbate,
nedsalk and
petertonysmith94
as code owners
arboleya
reviewed
Apr 30, 2024
arboleya
reviewed
Apr 30, 2024
danielbate
previously approved these changes
May 2, 2024
arboleya
requested changes
May 2, 2024
Co-authored-by: Anderson Arboleya <[email protected]>
arboleya
approved these changes
May 3, 2024
|
Coverage Report:
Changed Files:Coverage values did not change👌. |
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.
Closes #2203
Introduces a workflow to clean up potentially stale issues / bugs raised where we need author input to progress.
This workflow requires two new labels
need-author-inputandstaleSo the sequence of actions would be this:
need-author-inputlabelneed-author-inputlabel has been assigned to the issue, the countdown (of 14 days in this case) begins, after 14 days the label stale is assigned to the issue and a generated warning is commented by the github bot that the issue will close in 7 days