You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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):
The text was updated successfully, but these errors were encountered: