Yes, this sounds really good to me. As we now have a working Coder button to open our workspaces this becomes reality. Now that we can open a new workspace from an issue in github we are starting to have a lot workspaces at the same time in parallel.

Assigning @johnstcn

Similar questions to: #8098 (comment)

Workspaces are user-scoped, and each developer would like to pin their own. This does not need any organization. A simple feature that allows pinning one or more workspaces to stay permanently at the top of the table would solve this.

Thanks for the justification, @matifali.

I hope that we won't introduce Workspace folders soon :)

I'm going to be making some assumptions here:

1. Pinned workspaces should appear at the top of the workspaces list always, no matter if they are present in the regular list of workspaces.
2. Users can only pin/unpin workspaces to which they own (previously: have read update access).
3. Users will only see workspaces they themselves have pinned, and not pinned workspaces of other users.

@johnstcn I don't see any list of action items. Is the last part missing the UI implementation or is there something else?

@johnstcn I don't see any list of action items. Is the last part missing the UI implementation or is there something else?

Correct. Here's a list:

• Update DB schema + queries feat(coderd): allow workspace owners to mark workspaces as favorite #11791
• Add API endpoints to favorite/unfavorite workspace feat(coderd): allow workspace owners to mark workspaces as favorite #11791
• Add CLI commands to favorite/unfavorite workspace feat(cli): add favorite/unfavorite commands #11793
• Add UI support for favorites feat(site): show favorite workspaces in ui #11875
• Show favorite status in CLI: feat(cli): show workspace favorite status in list output #11878

@mtojek Can this be closed? We will probably have to iterate a little bit on the visuals but the fundamentals are done.

Yes, thank you for your contributions.