Skip to content
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.

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

Add support for --only flag that matches lerna/pnpm run behavior #174

Merged
merged 2 commits into from
Dec 10, 2021

Conversation

jaredpalmer
Copy link
Contributor

@jaredpalmer jaredpalmer commented Dec 10, 2021

Add a new --only flag to support restricting task execution to only the tasks specified in run. This is to make it easier to adopt turbo in a Lerna codebase since --only behavior is effectively an exact match.

For this pipeline:

"turbo": {
    "pipeline": {
      "build": {
        "outputs": [
          "dist/**/*"
        ],
        "dependsOn": [
          "^build"
        ]
      },
      "test": {
        "dependsOn": [
          "^build"
        ]
      }
    }
turbo run test

graph-1639160891531963000

turbo run test --only --graph

graph-1639160830365669000

@vercel
Copy link

vercel bot commented Dec 10, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/vercel/turbo-site/GssCk7G2x7sAiB4jdxwxMbWRPJ2V
✅ Preview: https://turbo-site-git-feat-only-flag.vercel.sh

@jaredpalmer jaredpalmer changed the title Feat/only-flag Add support for --only flag that matches lerna/pnpm run behavior Dec 10, 2021
@jaredpalmer jaredpalmer changed the title Add support for --only flag that matches lerna/pnpm run behavior Add support for --only flag that matches lerna/pnpm run behavior Dec 10, 2021
@jaredpalmer jaredpalmer merged commit bc05c83 into main Dec 10, 2021
@jaredpalmer jaredpalmer deleted the feat/only-flag branch December 10, 2021 18:36
sokra pushed a commit that referenced this pull request Oct 25, 2022
When pushing several changes to a pull request, I don't think we need to continue running the actions (particularly benchmarking) for the old commits. This should cancel any still-running workflows when a new commit is pushed.
sokra pushed a commit that referenced this pull request Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant