[Feature]: Filter by the current repository/working directory

[emocharnik]

Is your feature request related to a problem? Please describe.
Now the extension returns all workspaces available to the user, and it doesn't take into account the current context (repository, working directory, git branch). It overwhelms the workspaces' widget and forces users to apply filters on their own.

Describe the solution you'd like
I'd like the extension to read the current git config and current working directory and use this data for the workspace filter automatically. This will allow me to understand the current state of workspaces faster and take action if any of the workspaces have to be fixed/approved/etc.

Describe alternatives you've considered
Alternatively, we can add another filter just by repository (like environments filter), and implement automatic filtering by working directory in future releases.

Additional context
Feedback from the Mike Hodgkins:

Any ideas if our 3000 workspaces would cause adverse performance?
Some things I think would be cool:

• workspace list only shows workspaces that relate to the repo/directory I have open in VSCode.
• We’re doing a lot more monorepo stuff, and our main monorepo has 10+ workspaces connected to various subdirectories, so opening reponame/src/MyService/terraform as my VSCode working dir would list about 200 workspaces configured with those VCS settings.

Vote on this feature request
If you think this feature is valuable, please give this issue a 👍 thumbs up! The more votes, the higher the priority.

[penja]

@emocharnik How these filters should work in combination with others filters? Or you mean this filter must be applied by default

[emocharnik]

@penja I think it can be a separate setting of the extension, where users select the strategy: all or only workspaces created from the current repository.

[penja]

@emocharnik Do you mean the extension settings? Should these settings be enabled by default?

[emocharnik]

@penja yes, but I wouldn't enable it by default.