Skip to content

Improve error message for invalid .gitpod.yml configurations ("continue with default" options) #16236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
loujaybee opened this issue Feb 6, 2023 · 1 comment

Comments

@loujaybee
Copy link
Member

When you submit an invalid configuration to Gitpod, the error message, and the recovery mode are not entirely obvious. There have been cases where users have missed, or not understood the purpose of the "continue with default configuration" button, for instance seeking to go back to the last known working commit rather than trying to open in a recover mode that ignores the currently broken configuration. We should look to declutter this view, making:

  1. It clearer that an error has occurred, exactly why, and the action to be taken (see screenshots).
  2. The call to action (CTA) more obvious, "continue with default configuration" is not very clear.
  3. Removing other visual noise that distracts the user from the CTA.

Note, I'm not providing specific wording or designs here, different designs and wording would have to be tested + explored.

Error message for incorrect gitpod.yml Error message for failed workspace image build
image image
@loujaybee loujaybee changed the title Improve error message for invalid configurations Improve error message for invalid .gitpod.yml configurations ("continue with default" options) Feb 6, 2023
@stale
Copy link

stale bot commented May 9, 2023

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label May 9, 2023
@stale stale bot closed this as completed Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant