Allow workspace-relative paths in --filter

[ethanresnick]

Goals

I often have commands like turbo build --filter='./apps/*' that attempt to run some turbo task(s) on a specific set of packages by directory. However, currently, this command only works if I'm in the root directory of the repo, because the filter path is relative to cwd. However, I'd like to be able to have commands like this that can run successfully, regardless of my current working directory. That way, I can save the command under some alias, or share the command around my company, and not have to cd into a specific directory (or tell others that they need to do this) before the command will work.

Non-goals

Everything other than the specific scenario above.

Background

See goals.

Proposal

Turbo already seems to have a notion of the "root directory" (where the root package lives and the turbo.json file is), which seems to be captured by the --cwd option. So, I'd propose exposing that with some microsyntax that's usable in path-based filters. For example:

turbo build --filter='<TURBO_ROOT_DIR>/apps/*'

That's just one possible approach, though. I'm totally agnostic on the approach, but I would like to see a way to handle this use case.

[anthonyshew]

Would you be able to use turbo build --filter="$(git rev-parse --show-toplevel)/apps/*"?