chore: regularly close stale issues #2533
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
rauno56
changed the title
Codecov Report
@@ Coverage Diff @@
## main #2533 +/- ##
=======================================
Coverage 93.04% 93.04%
=======================================
Files 138 138
Lines 5093 5093
Branches 1096 1096
=======================================
Hits 4739 4739
Misses 354 354 |
obecny
approved these changes
Oct 22, 2021
vmarchaud
approved these changes
Oct 26, 2021
dyladan
approved these changes
Oct 27, 2021
|
edit: should have read the description :) |
MSNev
approved these changes
Nov 10, 2021
|
@rauno56 some reason this is a draft? I think i'd like to merge this if you're ready |
|
Wanted to give the setup in the other repo a few cycles before merging this, just in case... |
|
Nobody on the SIG call had any complaints about the contrib action so it should be good here. |
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.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.