renovate/.github/label-actions.yml

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


    Get your issue 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 issue 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    

'needs-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    

'retry latest version':
  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    

'pr: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    

'pr: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    

'pr: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

'needs-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'
    - 'priority-5-triage'
    - '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'
  lock: true
  lock-reason: 'resolved'

'format-code-comments':
  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