What agents should know before contributing
vercel/turborepo
Build system optimized for JavaScript and TypeScript, written in Rust
Read by Bluet from 2 files written for agents and 300 merged pull requests on 2026-09-24. Not reviewed by the maintainers.
Rules its files tell agents (2)
- CONTRIBUTING.md
shouldThe focused cargo build -p turbo builds just the turbo CLI and its dependencies, skipping the workspace's othe…
The focused cargo build -p turbo builds just the turbo CLI and its dependencies, skipping the workspace's other top-level targets (such as the LSP, schema generator, and N-API addon) that you don't need for CLI development. Use a plain cargo build when you want to build and verify every workspace member.
- CONTRIBUTING.md
shouldIf you find a problem with a community-supported template, we ask that you do not open a GitHub Issue for it.
[!IMPORTANT] As Turborepo usage has grown, the community has contributed more and more examples to the repository. While this is exciting for us on the core team, we're unable to maintain the full surface area of every example, given the constant updates across the breadth of tooling that Turborepo works with in the examples. > Because of this, a handful of the examples are explicitly marked as maintained by the core team. For the rest, we work with the community to keep them as up to date and correct as possible. If you find a problem with a community-supported template, we ask that you d
Decisions its pull requests settled (9)
- #13917Pass merge_base and allow_unknown_objects in signature order for task-level filter ranges
- #13932Normalize bare directory outputs when filtering dependencyOutputs hashes
- #13994Stream custom repository downloads to disk
- #14046Avoid duplicate interrupts during task shutdown
- #14027Share one repo index across same-package spec rehashes in watch mode
- #14067Fall back to the published tag when the dogfooded turbo version is unpublished
- #14070Run Go workspace formatting per module
- #14079Follow Go default binary output paths
- #14229Put version in `turbo query` JSON output instead of a separate banner