-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] Stale issues getting closed again by bot #2276
Labels
bug
Something isn't working
Comments
github-actions
bot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Aug 24, 2023
marcalff
added a commit
to marcalff/opentelemetry-cpp
that referenced
this issue
Aug 24, 2023
3 tasks
marcalff
added a commit
that referenced
this issue
Aug 24, 2023
marcalff
removed
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Aug 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #2165
At some point in the past, automatically closing stale issues was disabled in CI (#1453),
but it seems this change got lost after upgrading actions/stale in stale.yml to newer versions.
Automatically closing stale issues is not desirable, the issue can be relevant and valid, even if not worked on.
A typical example of old and valid issues that are worth keeping is #873, it would never have been found and fixed if automatically closed by the bot.
Looking at how many time the bot automatically closed #873, and how many times the issue had to be manually reopened, my opinion if that this bot is counter productive and should be disabled.
Marking issues as
stale
is ok, closing them is not.The text was updated successfully, but these errors were encountered: