Jürgen Leschner

Hi @ChristianHuff-DEV, Thanks for the feedback - you make valid points. Here are a couple of notes about the planned changes from Gitpod. Please note that these plans are not...

I think we should try to include the actual error text in the feedback report Information about the context would be good too e.g. to tell the difference between 404...

@laushinka I rebased and updated the werft flags in the description

Testing error reporting on workspace start with private repo ||| |-|-| |  |  |

This implementation works, but it is incomplete because the error message text is not included with the feedback. We either have to grab an image, or (better), extract the error...

Reopened - tracking PR #12258

Some thoughts about this: Changing the billing account is probably not the most helpful suggestion in this scenario since users are unlikely to be members of multiple billing accounts. In...

We recommend automating as much as possible, all the steps needed to rebuild your workspaces. That said, this does sound like the concept of [rebasing for buildpacks](https://buildpacks.io/docs/concepts/operations/rebase/) (cc: @csweichel)

@atduarte I suggest renaming this issue to "Auto-select workspace class based on system requirements in gitpod.yml" to match the [comment](#issuecomment-1168620579). Allowing users to configure their preferred workspace class is a...

Starting simple is 😎. How about allowing a list of preferred workspace classes (for portability / cross-compatibility).