chore: regularly close stale issues #697
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
Codecov Report
@@ Coverage Diff @@
## main #697 +/- ##
=======================================
Coverage 96.87% 96.87%
=======================================
Files 11 11
Lines 640 640
Branches 126 126
=======================================
Hits 620 620
Misses 20 20 |
obecny
reviewed
Oct 13, 2021
vmarchaud
approved these changes
Oct 17, 2021
blumamir
approved these changes
Oct 18, 2021
dyladan
approved these changes
Oct 25, 2021
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.
Which problem is this PR solving?
We have an increasing number of unattended issues. Some of them are still relevant, many aren't. Setting up automation will ping the authors and participants to make sure there's either advancement on the issues/PRs or those will be cleaned up.
Adding
never-stalelabel to either an issue or a PR will disable that feature. Issues withinstrumentation-requestlabel are excluded by default, but I'm open to remove that exemption.The job is run weekly. The first run will be painful and will mark many issues stale once.