quarkusio / quarkusio/quarkus-github-bot

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

Open
#332 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
30
Forks
30
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named in the issue. Start by locating the lottery report implementation and the logic that reads issue comments; define how likely closure intent is identified and when a reminder should appear, then verify the behavior with tests for the proposed heuristics.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.