build-check

Automated build verification checks source code for compilation errors, type errors, and lint warnings across API and web services before testing or deployment. It identifies services automatically based on directory structure or configuration files to ensure readiness.

Running a build verification process is the best way to check for compilation and type errors before deployment. It captures and reports detailed lint warnings and errors, providing clear troubleshooting details to prevent deployment failures.

Docker is not required to run automated build checks. You need local environment setup for build tools to verify compilation and type errors, while Docker is optional and only needed if you want to run containerized builds.

Yes, you can use build verification to check both API and web services simultaneously. It automatically identifies different service types from your directory structure and reports any compilation or lint issues found across all detected services.

Automated build verification identifies services based on your directory structure or specific configuration files. If your project lacks these standard structural markers, the verification process will fail to detect and check your API and web services.