Gp validate is included in every workspace. The new Gitpod command gp validate allows you to do exactly this: validate your configuration changes without committing, or leaving your workspace! Which is why we are “shifting left” and bringing errors, validation and suggestions closer to when you are actually developing on and iterating on your configuration. This process would delay the time to finding out a configuration was incorrect, and in the mean time pollute your source control with commits like: ” updates”, ” next”, ” please work!”, ” please work this time” - yeah, we know how it feels! To update a configuration, you would commit your. Because, when your workspace is configured, you can make use of ephemeral workspaces, multi-track development and other benefits of developing in the cloud. The power of a CDE comes with a well-defined configuration.

Using gp validate -prebuild you can create run a workspace just as a Prebuild would, which makes it easier to debug a Prebuild configuration by re-creating the exact state inside a running workspace.

This works in a very similar way to a regular Gitpod workspace start, allowing you to catch configuration mistakes earlier. With gp validate can now validate a configuration within the workspace without committing.gitpod.yml and the workspace image-by running gp validate without needing to restart, leave your workspace, or commit your configuration. TL DR - You can now validate a Gitpod configuration-both the.

Download gitpod phpstorm