Mohamed Hubail

@SimenB From what I can find, the docker file was almost done in #13009, but was held back because `yarn watch` command was not working. Would it be of interest...

@jayair If there's interest I can submit a PR to add this option to `dev` command.

I'm interested in picking this up. ~~I've looked around in the codebase. What I have in mind is to add the filtering in [`packages/vitest/src/node/workspace.ts`](https://github.com/vitest-dev/vitest/blob/95f0203f27f5659f5758638edc4d1d90283801ac/packages/vitest/src/node/workspace.ts#L331-L354); and to use `getTests()` from `packages/runner/src/utils/tasks.ts`...

@arcanis Any updates on this? Since last update the options `--since` and `--recursive` has been added for `yarn workspaces list` and `yarn workspaces foreach` which covers part of the functionality...

- For now I'm not sure if this option should be added to all commands that have auditing (similar to how `--audit-format` is implemented. I'd like input on that. If...

> I assume git config affects this, i'm not sure if the default git config behavior of opening a new instance could be overriden? I think you can set `GIT_EDITOR`...

> I would prefer if we passed down locations there to keep the scope clean and avoid polluting the config. As far as I can tell, `globTestSpecs` is run before...

I might be missing something. What kind of information do I have access to in a spec? How would I access the line numbers of a test? I see `location`...

> You can keep the filtering in the test like it is, but change how the values are passed down from the main process. Do you mean that the issue...

Yeah, that makes sense. I'll take a shot at it.