registry: add turbo

[igas]

https://turborepo.dev/

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates Turborepo into the project's registry by adding its configuration. This enables the system to recognize and utilize Turborepo as a backend for managing JavaScript and TypeScript monorepos, aiming to streamline build processes and enhance performance.

Highlights

• New Tool Integration: Added Turborepo (turbo) to the registry, making it available as a high-performance build system backend.

Changelog

• registry/turbo.toml
  • Added a new configuration file for Turborepo, defining its backend, description, and a test command.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[greptile-apps]

Greptile Summary

This PR adds a new registry entry for Turborepo, a high-performance monorepo build system for JavaScript/TypeScript, backed by the npm:turbo package. The entry follows the established conventions in the registry (matching recent additions like portless.toml) and is correctly structured.

• backends = ["npm:turbo"] correctly points to the official Turborepo CLI package on npm
• The description is accurate
• test = { cmd = "turbo --version", expected = "{{version}}" } matches the expected output format of turbo --version (plain version string)
• A detect field (e.g. detect = ["turbo.json"]) is absent — adding it would enable auto-activation in Turborepo projects, consistent with how similar tools are configured

Confidence Score: 4/5

• This PR is safe to merge; it adds a well-formed registry entry following existing conventions.
• The single changed file is a small, correctly-structured TOML registry entry that follows the same pattern as other recent npm-backed additions. The only missing element is an optional detect field.
• No files require special attention.

Important Files Changed

Filename	Overview
registry/turbo.toml	New registry entry for Turborepo using npm:turbo backend with correct format and description; missing detect field for turbo.json auto-detection.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[mise install turbo] --> B{Backend resolution}
    B --> C[npm:turbo]
    C --> D[Install turbo package via npm]
    D --> E[turbo binary available on PATH]
    E --> F{Test verification}
    F --> G["turbo --version → matches {{version}}"]
    G --> H[Installation verified ✓]

Loading

_{Last reviewed commit: eaf34cd}

[greptile-apps]

Missing detect field for turbo.json

Turborepo projects typically include a turbo.json configuration file at their root. Adding a detect field would allow mise to automatically activate this tool when users are inside a Turborepo project, consistent with how other tools like bun (which detects bun.lock, bun.lockb, bunfig.toml) handle project-level activation.

Suggested change

	backends = ["npm:turbo"]
	description = "Turborepo is a high-performance build system for JavaScript and TypeScript codebases."
	test = { cmd = "turbo --version", expected = "{{version}}" }
	backends = ["npm:turbo"]
	description = "Turborepo is a high-performance build system for JavaScript and TypeScript codebases."
	detect = ["turbo.json"]
	test = { cmd = "turbo --version", expected = "{{version}}" }

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[gemini-code-assist]

Code Review

This pull request adds turbo (Turborepo) to the tool registry, making it installable via the npm backend. The configuration is straightforward and looks good, but I've identified a potential issue with the test command's expected output which may cause the post-installation test to fail. My review includes a suggestion to resolve this.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

The test command turbo --version outputs a string that includes more than just the version number (e.g., @turbo/cli/1.13.3 darwin-arm64). The expected = "{{version}}" check will likely fail because it expects an exact match with the version string (e.g., 1.13.3).

To ensure the test passes, I recommend removing the expected field. The test will then simply verify that the command executes successfully (with a zero exit code), which is a sufficient check for a successful installation.

Suggested change

	test = { cmd = "turbo --version", expected = "{{version}}" }
	test = { cmd = "turbo --version" }

[igas]

It does print:

$ turbo --version
 WARNING  No locally installed `turbo` found. Using version: 2.5.3.
2.5.3

But in the real example where turbo installed in the repo:

$ turbo --version
2.8.13