gitpod-io / gitpod

The developer platform for on-demand cloud development environments to create software faster and more securely.
https://www.gitpod.io
GNU Affero General Public License v3.0
12.57k stars 1.2k forks source link

Improve paused prebuilds alert #14294

Open gtsiolis opened 1 year ago

gtsiolis commented 1 year ago

Problem to solve

Following up from https://github.com/gitpod-io/gitpod/pull/14081, the new paused prebuilds alert successfully informs users about this system change and provides an action to resolve the alert.

However, there are a couple of issues that come with the current approach:

  1. The paused prebuilds alert is not visible in the prebuilds page, which is the most relevant page for this message.
  2. The latest prebuild information on the project card is accurate, but possibly irrelevant and not useful.
  3. Clicking the action (link button) to resume prebuilds, breaks the layout of the alert message, keeps the alert on visible, is updating the link color to be the same as the rest of the alert message, etc.

See also relevant discussion (internal). Cc @AlexTugarev @jldec

Branches (project default page) Prebuilds Project Resuming Prebuilds
paused-1 paused-2 Screenshot 2022-10-31 at 5 22 41 PM Screenshot 2022-10-31 at 5 33 29 PM copy

Proposal

TBD (To be discussed)

In the meantime, here are two approaches to consider doing as minimal viable changes (MVCs):

:a: Move the alert to the top of the prebuilds list as an in-page alert.

:b: Move the alert to the top of the branches and prebuilds page.

In both cases :a:/:b:, there's no need to maintain the trigger state inside the alert when resuming prebuilds. Instead, we could a) redirect to project prebuilds and b) populate the prebuilds list with the newly triggered prebuild as user feedback.

Other things to consider for next iterations include updating the project card so that the prebuilds paused state is also visible from the team page where all projects are listed. ➰

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.