renovate/.github/label-actions.yml

'auto:reproduction':
  comment: >
    Hi there,


    Get your discussion fixed faster by creating a minimal reproduction.
    This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.


    Before we start working on your issue we need to know exactly what's causing the current behavior.
    A minimal reproduction helps us with this.


    To get started, please read our guide on creating a [minimal reproduction](https://github.com/renovatebot/renovate/blob/main/docs/development/minimal-reproductions.md).


    We may close the discussion if you, or someone else, haven't created a minimal reproduction within two weeks.
    If you need more time, or are stuck, please ask for help or more time in a comment.


    Good luck,


    The Renovate team    

'auto:logs':
  comment: >
    Hi there,


    This issue or discussion is missing some logs, making it difficult or impossible to help you.
    Depending on which situation applies follow one, some or all of these instructions.


    ### No logs at all

    If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.


    #### Finding logs on hosted app

    <details><summary>Select me to read instructions</summary>


    If you use the Renovate app (GitHub):

    1. Go to the affected PR, and search for "View repository job log here"

    1. Select the link to go to the "Mend Renovate Dashboard" and log in

    1. You are now in the correct repository log overview screen

    1. Copy/paste the correct log

    1. Follow the steps in the **formatting your logs** section

    </details>


    #### Finding logs when self-hosting

    <details><summary>Select me to read instructions</summary>


    If you're running self-hosted, run with `LOG_LEVEL=debug` in your environment variables and search for whatever dependency/branch/PR that is causing the problem.

    </details>


    ### Insufficient logs

    <details><summary>Select me to read instructions</summary>


    If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the **No logs at all** section.

    </details>


    ### Formatting your logs

    <details><summary>Select me to read instructions</summary>


    Please put your logs in a `<details>` and `<summary>` element like this:


        <details><summary>Select me to see logs</summary>

        ```
        Copy/paste your logs here, between the starting and ending backticks
        ```

        </details>

    </details>


    Good luck,


    The Renovate team    

'new package manager':
  comment: >
    Hi there,


    You're asking us to support a new package manager.
    We need to know some basic information about this package manager first.
    Please copy/paste [the new package manager questionnaire](https://github.com/renovatebot/renovate/blob/main/docs/development/new-package-manager-template.md), and fill it out in full.


    Once the questionnaire is filled out we'll decide if we want to support this new manager.


    Good luck,


    The Renovate team    

'auto:retry-latest':
  comment: >
    Hi there,


    You're reporting a problem with an old version of Renovate.
    Please try the latest version and tell us if that fixes your problem.


    Good luck,


    The Renovate team    

'auto:no-coverage-ignore':
  comment: >
    Hi there,


    You're skipping code tests with `istanbul ignore`.


    Please only skip tests if:
     - you cannot test the code, or
     - the code is very difficult to test, or
     - the edge case won't usually happen at runtime


    If you skip a test, always comment why:


    ```ts
    // istanbul ignore next: typescript strict null check
    if (!url) {
      return null;
    }
    ```


    Good luck,


    The Renovate team    

'auto:no-done-comments':
  comment: >
    Hi there,


    You are using `done` comments which cause a lot of noise.
    Instead, please use GitHub's web interface to request another review.
    Please read our [contributing guidelines](https://github.com/renovatebot/renovate/blob/main/.github/contributing.md#resolve-review-comments-instead-of-commenting) to reduce noise.


    Good luck,


    The Renovate team    

'auto:discussion-first':
  comment: >
    **Please create a GitHub Discussion before continuing with this PR.**


    Thank you for your PR, but we need to discuss the requirements and implementation first.
    This PR will be closed, but you can reopen it after the discussion has been resolved.


    Thanks, the Renovate team    
  close: true

'auto:more-details':
  comment: >
    Hi there,


    This discussion is missing some details, making it difficult or impossible to help you.
    Please try again to provide more details.    

'needs-discussion':
  unlabel:
    - 'type:bug'
    - 'type:feature'
    - 'status:requirements'
  comment: >
    **Please create a GitHub Discussion instead of this issue.**


    We only want Renovate maintainers to create new Issues. If needed, a Renovate maintainer will create an Issue after your Discussion been triaged and confirmed. As a Renovate user, please create a GitHub Discussion in this repo instead.


    This Issue will now be closed and locked. We may later batch-delete this issue. This way we keep Issues actionable, and free of duplicates or wrong bug reports.


    Thanks, the Renovate team    
  close: true
  close-reason: 'not planned'

'auto:format-code':
  comment: >
    Hi, please format any copy/pasted code or logs so they're readable.


    You can find a Markdown code formatting guide [here](https://www.markdownguide.org/basic-syntax/#code) as well as some GitHub-specific information formatting code blocks [here](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks).


    Thanks, the Renovate team    

'auto:discussion-closed':
  comment: >
    Hi there,


    We're closing this discussion because it's missing some details, or because something else about it made it hard or impossible for us to help resolve the issue.


    We want high quality discussions, so users can search them for answers.
    This means we'll close (and later delete) low quality discussions.


    You are welcome to create a new discussion with more details in future.


    Thanks, the Renovate team.    
  close: true
  close-reason: 'not planned'

'auto:bad-vibes':
  comment: >
    Hi there,


    A maintainer has flagged this discussion as giving off some bad vibes. **Maintainers will no longer participate in this discussion unless/until such "vibes" are resolved.**


    This is typically when someone is overly critical of the product or the assistance they're receiving.
    Or being unreasonably demanding or lazy, such as refusing to provide logs, or other information, when asked.


    Open Source means you're welcome to use the software with few limits applied.
    But you should _not_ give maintainers a bad day or contribute to Open Source burnout.


    If you feel this message is wrong or due to a misunderstanding, please let us know. If you see this message but don't take it as a sign to cool off or back off, we may close the discussion and block you from the repository.


    If you want to get the discussion back on track, we would like you to:
     - Remove, or edit, the bad vibes parts of your comments
     - Say that you understand the problem (we don't need a lengthy apology)
     - Stop giving off more bad vibes


    If you're unhappy with this, we suggest you stop using the repository discussions or the product altogether.


    Thanks, the Renovate team    

'auto:one-topic':
  comment: >
    Hi there,


    Please stick to one topic/question per Discussion. Start a new discussion per topic.


    This prevents future users from finding this discussion and getting confused by multiple questions and answers. One question and answer per Discussion works best.


    For example:
     - Don't create a discussion with multiple questions requiring multiple answers
     - If you got an answer to your first question, don't change topic like "Can I also ask you how I might..." which would then require a different answer. Mark the current discussion as answered and open a new one.


    Thanks, the Renovate team    

'auto:no-mentions':
  comment: >
    Hi there,


    Please do not unnecessarily `@` mention maintainers like `@rarkins` or `@viceice`. Doing so causes annoying notifications and makes it harder to maintain this repository.


    For example, never `@` mention a maintainer when you are creating a discussion if your desire is to get attention. This is rude behavior, just like shouting out your coffee order in a Starbucks before it's your turn.


    It's OK to comment in an issue or discussion after multiple days or weeks. But please, still don't `@` mention people. The maintainers try to answer most discussions, but they can't answer all discussions. If you're still not getting an answer, take a look at the information you've given us and see if you can improve it.


    Thanks, the Renovate team    

'auto:misclassified-problem':
  comment: >
    Hi there,


    A maintainer has flagged that this discussion is _misclassified_ as a bug when it is not.


    Incorrectly classified discussions waste maintainer time, worsen search result accuracy and make it harder to train AI on this dataset.


    The next time you create a discussion, please keep in mind:
     - If you are new to Renovate, try to stick to questions instead of problem reports
     - Just because Renovate does something you don't expect, doesn't automatically mean it's a bug
     - Unsupported features should be raised as ideas, not problems
     - Those who appear to be _twisting_ questions into sounding like a bug for attention will be given the least support

    Thanks, the Renovate team