Skip to content

Change the "needs info" message depending on the other labels #62

Closed as not planned

Description

@not-an-aardvark

When someone adds the needs info label, the bot's message is intentionally very generic, because we sometimes aren't sure what an issue is trying to do at all. However, there are other cases where the type of an issue is clear, but not enough information has been provided to respond to it (e.g. if the issue is proposing a new behavior but is insufficiently detailed about what the new behavior is). In these cases, the generic "needs info" message isn't as applicable.

It would be nice if the bot looked at the other labels on the issue, and gave a specialized message. For example, if enhancement, rule, and needs info were added at the same time, the bot would ask the user to fill out the rule change proposal template. If bug and needs info were added at the same time, the bot would ask the user to fill out the bug report template.

Activity

  1. platinumazure commented on May 23, 2018

    @platinumazure
    Member

    Question: Should the bot be agile enough to edit its own message as the labels change? (e.g., if we started with triage/needs info and then edited to be bug/evaluating/needs info, it could edit its previous message with the bug report template)

  2. not-an-aardvark commented on May 23, 2018

    @not-an-aardvark
    MemberAuthor

    I suppose that would be nice, although it's probably not required for the plugin to be useful if it would be easier to implement without that feature.

  3. kaicataldo commented on Oct 28, 2018

    @kaicataldo
    Member

    I wonder if it being "dumber" is actually better in this case - i.e. it creates a new comment with the relevant information whenever the "needs info" label is added based on whatever labels it has at that moment. I think it'll make easier to understand for those viewing the conversation after the fact.

  4. github-actions commented on Aug 14, 2025

    @github-actions

    Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update.

  5. github-actions commented on Aug 22, 2025

    @github-actions

    This issue was auto-closed due to inactivity. While we wish we could keep responding to every issue, we unfortunately don't have the bandwidth and need to focus on high-value issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions