[Projects/branches] UX confusion: "commit" is assumed to match "prebuild"
Open
Nobody has claimed this yet.
component: dashboard
meta: never-stale
type: improvement
user experience
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
In this view users often assume that what they see as "commit" is the basis for the prebuild that's linked under the "prebuild state" (here: running).
This is not true:
- the Git state is fetched from the hoster directly, and represents the latest HEAD state
- prebuild is just the latest prebuild
Depending on how quick we are with picking up work on new commit events (or if the webhook mechanism works) this might or might not match.
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 inspecting the Projects/branches view shown in the issue and trace how the displayed commit and prebuild state are sourced. Determine a UI treatment that makes their different meanings clear; done means users can distinguish the latest hoster HEAD from the latest prebuild without assuming they match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100