gitpod-io / gitpod-io/gitpod

Rename the prebuild trigger action

Open
#5,008 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component: dashboard feature: prebuilds feature: teams and projects [DEPRECATED] meta: never-stale team: webapp user experience
Dominant language
TypeScript
Stars
13.8k
Forks
1.4k
Avg merge
17h 58m
Merged PRs (30d)
5

Description

Problem to solve

Using the the verb trigger as a call-to-action may be confusing or complex for some users, see relevant discussion:

George: What do you think of renaming the action verb to Run and change this to Run Prebuild to make it sound less complex? We can keep the metadata information with the same verb (Triggered 2 minutes ago). Maybe also something to change in a future iteration.

Jan: Ah, I was confused by what this "Trigger Prebuild" meant. What is the intent? Is it to "Re-try Failed Prebuild"?

Cc @jankeromnes @AlexTugarev

Proposal

We could rename the call to action verb to Run so that Trigger Prebuild becomes Run Prebuild. 🏃

We also need to take into account how we use this verb when retrying a successful or failed prebuild. ❓

TBD (To be discussed)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the UI text "Trigger Prebuild" and tracing how the action is presented when retrying successful or failed prebuilds. Confirm the intended wording with the linked discussion, then consider the work done when the call-to-action and its retry variants use the agreed terminology consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.