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

Comment on issues that were meant to be closed but were not #332

Open
geoand opened this issue Apr 12, 2023 · 0 comments
Open

Comment on issues that were meant to be closed but were not #332

geoand opened this issue Apr 12, 2023 · 0 comments

Comments

@geoand
Copy link

geoand commented Apr 12, 2023

As Quarkus maintainers we often decide to close issues that perhaps invalid, out of date or lack proper information.
While doing this, I noticed a user error on our part that happens every now and then and which I think the bot can help with:

There are times as one of us members comments that we are closing the issue for this or that reason, but then we actually forget to.

It bot could add a ping that we likely wanted to close but forgot to do so.

There are various questions that need to be addressed (which we can likely apply some simple heuristics for initially and then improve if necessary):

  • How do we determine that a maintainer intended to close an issue? Likely by looking at the last comment for keywords and checking whether it's a statement and not a question.
  • When should this check occur? The easiest way is probably to include it in the lottery report
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant