Consider merging the unified workspaces list
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Back in https://github.com/gitpod-io/gitpod/pull/5555, we've decided to merge the two Workspaces lists (Active, All) into one. However, we've split the list into two parts where active and pinned workspaces are grouped at the top of the page while stopped and inactive workspaces at the bottom of the list.
This is a follow-up issue to continue the discussion in https://github.com/gitpod-io/gitpod/pull/5555#discussion_r715036381 regarding merging the unified workspaces list into one list.
thought: Wondering if making this element sticky at the top of the list and removing the pinning functionality altogether could be better. Do we have data on how many pinned workspaces are out there?
BEFORE AFTER
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request #5555 and the linked discussion to understand the prior workspace-list decision and the remaining alternatives. Determine the intended product direction for combining the lists, including whether pinning should remain; done means the decision and resulting scope are documented clearly enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100