Skip to content
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

Enable no-response bot to auto close inactive issues #2928

Merged
merged 3 commits into from
Jan 23, 2024

Conversation

testforstephen
Copy link
Collaborator

Signed-off-by: Jinbo Wang [email protected]

It auto closes those inactive issues:

  • Marked as "need info"
  • Inactive for 14 days

@fbricon
Copy link
Collaborator

fbricon commented Feb 9, 2023

I think we need to manually go over all of https://github.com/redhat-developer/vscode-java/issues?q=is%3Aopen+is%3Aissue+label%3A%22need+info%22 to check if users actually gave some info, and remove the label if needed, before we apply this action.

@rgrunber rgrunber force-pushed the jinbo_noresponsebot branch from 9d331da to 829e528 Compare January 23, 2024 20:49
@rgrunber
Copy link
Member

rgrunber commented Jan 23, 2024

I've gone over all the need info labels. I definitely learned some interesting things along the way and for the most part I've either :

  • Removed need info because additional info was given, or I felt there was enough info that an investigation at a later time was worth it
  • Closed the issue because it was either a duplicate, or it was very similar to issues we fixed in the past, etc.
  • Left the issue because it had need info, no response / no meaningful information to make any progress, so we can leave it to the bot as a testcase 😜

I've also bumped the "days inactive" for auto-close to 30, as 14 seemed a bit too short.

@rgrunber rgrunber merged commit 9ab7039 into redhat-developer:master Jan 23, 2024
2 checks passed
@testforstephen testforstephen deleted the jinbo_noresponsebot branch January 24, 2024 01:40
@rgrunber rgrunber self-assigned this Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

3 participants