Michael Brewer

Yes, currently these workspaces are opened from "Open in Coder" or via an inhouse Chrome extension. As a chrome extension As from Open in Coder

For now : I can pass in the "repo_name" to refill the workspace name for now. Also for an open workspace I will see if I can add meta-data fields...

Could be i will try it out. I assume you can use this to filter workspaces by a parameter name? like repo url.

@BrunoQuaresma - would this filter pick up workspace metadata as well? For example we could flag that a workspace has uncommitted work, so we don't want to delete these unnecessarily....

Awesome a good start :)

Nice @BrunoQuaresma i tested it how, only problem is that requires exact match, so for git_repo urls you have to do `owner:me param:"git_repo=https://github.com/microsoft/vscode-remote-try-go"` But it would be nice to do...

@Emyrk possibly. If there is no concerns with performance. Visually having an option to select additional fields would be great. Search and filtering is useful for looking across an entire...

My use-case is the ux of when you have 2 or more workspaces stopped or listed on the dashboard. Users would not know which workspace is for which work. Generally...

for collections of repos, users creating a workspace should name it clearly. But short lived workspaces or tasks that can operate on a single repo having access to fields to...

also often to run diagnostics on a running workspace (or one that failed to start currently..), has to be done via kubectl. The ability for a template to expose these...