chore: regularly close stale issues #2533
Merged
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-stale
label to either an issue or a PR will disable that feature.The job is run weekly. The first run will be painful and will mark many issues stale once.
There's a companion PR for contrib: open-telemetry/opentelemetry-js-contrib#697
I'd leave this one as a draft for now and see how it goes in the first week or two in contrib, not to overwhelm ourselves.