这是indexloc提供的服务，不要输入任何密码
Skip to content

docs(guides): give appropriate attribution to Microsoft Lage #370

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 20, 2021
Merged

docs(guides): give appropriate attribution to Microsoft Lage #370

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/pages/docs/features/pipelines.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@ title: Pipelines

import Callout from "../../../components/callout";

<Callout>
This page and Turborepo's Pipeline API design was copied from the Microsoft Lage [Pipelines Page](https://microsoft.github.io/lage/guide/pipeline.html#defining-a-pipeline).
</Callout>

# Pipelining Package Tasks

In traditional monorepo task runners, like `lerna` or even `yarn`'s own built-in `workspaces run` command, each NPM lifecycle script like `build` or `test` is run [topologically](./glossary#topological-order) (which is the mathematical term for "dependency-first" order) or in parallel individually. Depending on the dependency graph of the monorepo, CPU cores might be left idle—wasting valuable time and resources.
Expand Down
4 changes: 4 additions & 0 deletions docs/pages/docs/features/scopes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,10 @@ title: Scoped tasks

import Callout from "../../../components/callout";

<Callout>
This page and Turborepo's Scoped Tasks API design was copied from the Microsoft Lage [Scoped Builds Page](https://microsoft.github.io/lage/guide/scopes.html#scoped-builds-with-all-its-dependents).
</Callout>

# Scoped Tasks

Scoping task execution can speed up the process especially if there are distinct clusters of packages that are not related to each other within your repository. Turborepo has a `scope` option that allows the task running to proceed up to the packages found that matches the `scope` argument. It's useful to think of `scope` as an "entry point" into your monorepo's package/task graph. This is a string matcher based on the name of the packages (not the package path).
Expand Down