GitHub Source Build V2 inspection
BetaBeta inspection verifies repository access, branch, exact commit, project root, framework, package manager, build script, output, and environment-variable references before any runner dispatch; compilation is planned and disabled.
What this does
Creates a stable source snapshot and controlled build configuration for the future isolated V2 runner.
What you need
A readable repository, branch, compatible static web build, and connected GitHub account.
What LaunchLayer automates
Permission check, default-branch and commit resolution, file evidence, framework hints, lockfile priority, and configuration proposal.
What remains external
Secret values, GitHub Actions capacity, platform signing, and device testing.
Exact setup steps
Connect GitHub, open Cloud Build, inspect source, choose a project root when prompted, review commands and output, then confirm configuration.
How to verify it
Confirm the displayed owner, repository, branch, commit SHA, framework evidence, and output directory match the intended release source.
Common failures
Wrong account, inaccessible private repository, wrong branch, truncated tree, missing build script, or server-required framework.
Security considerations
LaunchLayer reads source metadata through the current app user's connector and never executes repository code in the application backend.
Related articles
Repository permissions; framework detection and monorepos; Cloud Build stages.