Unify affected git-range arguments across run, query, and ls

[voiys]

turbo query affected supports explicit --base and --head arguments:

turbo query affected --base origin/develop --head HEAD

However, turbo run --affected requires the equivalent range through environment variables:

TURBO_SCM_BASE=origin/develop TURBO_SCM_HEAD=HEAD turbo run test --affected

Could --base and --head be supported consistently across run --affected, query affected, and ideally ls --affected?

The existing environment variables should remain supported. Explicit flags could follow query affected’s current precedence and override them.

This would make the range visible in the command itself, discoverable through --help, and easier to configure in CI.

Tested with Turborepo 2.10.5.

[anthonyshew]

We do feature requests in Discussions, so I'll move this there.

[Divyansh151005]

I'd like to take this on.

Understanding: turbo query affected already accepts --base / --head (CLI overrides TURBO_SCM_*), but turbo run --affected and turbo ls --affected only read the env vars today.

Approach:

• Add --base / --head to run/watch (ExecutionArgs) and ls (including query ls)
• Reuse the same precedence as query affected: CLI flags override TURBO_SCM_BASE / TURBO_SCM_HEAD
• Add CLI parse tests + affected integration coverage mirroring the existing SCM env override tests

I'll open a PR once tests pass locally.

[Divyansh151005]

Opened #13884 with --base / --head for run --affected and ls --affected, matching query affected precedence.

[Divyansh151005]

Correction: the PR is #13885 (not 13884).