Yaohui Wang

> **1. Does it happen only if a user has .gitpod.yml opened? Can we run this inspection automatically on startup that a warning is visible in Problems even if .gitpod.yml...

un-draft to move forward with CR

Hi Anton, > * if a file does not exist then show a notification about issues with .gitpod.yml and suggest an action to create it and fix issues automatically Notification...

Run inspection automatically on startup implemented at https://github.com/gitpod-io/gitpod/pull/11089/commits/49a4935a373a2bde96464cf58caca27fb9509daa

This PR is getting larger, I'll leave some notes for ease of CR: Known Issues: 1. [ApplyVMOptionsQuickFix](https://github.com/gitpod-io/gitpod/pull/11089/files#diff-21237827a9d6e504e14cf7f30bc0f5db266e77dbd9480580b5a6f4e1427b27c0) is not used. It could be removed or kept in case the IDE...

> @yaohui-wyh Sorry I did not have time to try earlier. I'm trying to build but it fails [[1](https://werft.gitpod-dev.com/job/gitpod-build-yh-backend-plugin-inspection-fork.0/raw)] Fixed. PTAL:)

> @yaohui-wyh It's still failing: https://werft.gitpod-dev.com/job/gitpod-build-yh-backend-plugin-inspection-fork.1/raw sorry for long turnarounds The build failure might be caused by other components which this PR didn't touch (failed at leeway `buildGo` step )....

The build failure is still irrelevant to the PR (`no space left` for the build agent), maybe rerun werft job on another node? ``` ... [components/ide/jetbrains/image:intellij] failed to copy files:...