name: Turborepo bug report
description: Create a bug report
labels: ["kind: bug"]

body:
  - type: markdown
    attributes:
      value: |
        This template is to report bugs. Before opening a new issue, please do a [search](https://github.com/vercel/turborepo/issues) of existing issues and :+1: upvote the existing issue instead. This will result in a quicker resolution.

        If you need help with your own project, you can:
        - Start a discussion in the ["Help" section](https://github.com/vercel/turborepo/discussions/categories/help).
        - Ask a question in [the Turbo Discord server](https://turbo.build/discord).

  - type: checkboxes
    attributes:
      label: Verify canary release
      description: "Please install the canary version of `turbo` using your package manager (e.g. `npm install turbo@canary`) to try the canary version of Turborepo. It includes all features and fixes that have not been released to the stable version yet. Some issues may already be fixed in the canary version, so please verify that your issue reproduces before opening a new issue."
      options:
        - label: I verified that the issue exists in the latest Turborepo canary release.
          required: true

  - type: input
    attributes:
      label: Link to code that reproduces this issue
      description: |
        A link to a **public** GitHub repository with a minimal reproduction. Ideally, minimal reproductions should be created using [`npx create-turbo@canary -e with-shell-commands`](https://github.com/vercel/turborepo/tree/main/examples/with-shell-commands) and should include only changes that contribute to the issue. You may also use [`npx create-turbo@canary -e <example-name>`](https://github.com/vercel/turborepo/tree/main/examples) to create a reproduction that includes frameworks if you believe your bug requires a specific framework to reproduce.
    validations:
      required: true

  - type: input
    attributes:
      label: Which canary version will you have in your reproduction?
      description: |
        To find the exact version installed in your reproduction, you can use `npm list turbo`, `yarn why turbo`, or `pnpm why turbo`.
    validations:
      required: true

  - type: textarea
    attributes:
      label: Environment information
      render: block
      description: |
        Run the command `turbo info` and paste its output here. Please review it in case there is sensitive information you don't want to share.

  - type: textarea
    attributes:
      label: Expected behavior
      description: |
        A clear and concise description of what you expected to happen.
    validations:
      required: true

  - type: textarea
    attributes:
      label: Actual behavior
      description: |
        A clear and concise description of the bug.
    validations:
      required: true

  - type: textarea
    attributes:
      label: To Reproduce
      description: |
        Steps to reproduce the unexpected behavior. Please provide clear code snippets that always reproduces the issue or a GitHub repository. Screenshots can be provided in "Additional context" below.
    validations:
      required: true

  - type: markdown
    attributes:
      value: |
        Another way you can help the maintainers is to pinpoint the `canary` version of `turbo` that introduced the issue. Check out our [releases](https://github.com/vercel/turborepo/releases), and try to find the first `canary` release that introduced the issue. While not required, this will help us narrow down the scope of the issue, and possibly point to the PR/code change that introduced it. You can install a specific version of `turbo` by running `npm install turbo@<version>` or the equivalent for your package manager.
  - type: textarea
    attributes:
      label: Additional context
      description: |
        Any extra information that might help us investigate. For example, where are you deploying your application (Vercel, Docker, other platform)? Is it only reproducible on that platform, or locally too? Is the issue only happening in a specific browser? etc.
      placeholder: |
        I tested my reproduction against different canary releases, and the first one that introduced the bug was "2.2.4-canary.2", since reverting to "2.3.4-canary.1" works.
        or
        I am using GitHub Actions but running my tasks locally does not have the same issue.
