Improve the context column information
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
The design specs in #3426 for the new Workspaces list contained some structure and labels for the Context URL. For the time being, we're surfacing the context URl which overflows on smaller viewports and includes some duplicate information with the Pending Changes column on the right.
Proposal
More particularly, on the second column, a) the context URL should not include the branch name, b) the context URL should surface the commit message, and c) the subtitle should be more semantic like Pull Request 324,.
Designs
Attaching below an early design spec for this proposal, see Context column. /cc @svenefftinge
| BEOFRE | 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 locating the Workspaces list and its Context column implementation; the issue provides no file or test names. Compare the current column with the attached design, then verify that the URL omits the branch name, shows the commit message, and uses a semantic subtitle such as “Pull Request 324” without overflow or duplicate pending-change information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100

