Deploy the artifact, not the repository
Keep prebuilt delivery separate from source builds and their dependency graph.
Deploys a verified local build artifact to Netlify without asking Netlify to rebuild the source project.
Deploying an already-built application through a source-oriented hosting flow can trigger unnecessary rebuilds, publish the wrong directory, or upload unsafe local artifacts.
The requested artifact must be validated before any remote mutation.
Secrets, source trees, caches, and unrelated files must never enter the deploy payload.
Site selection, production promotion, and deployment are separate authorization boundaries.
Local artifact and publish-directory preflight; Netlify CLI flow selection with explicit mutation gates; deployed URL and content verification.
Validate the artifact tree, entry points, size, and excluded content.
Choose the correct draft or production Netlify CLI path only after authorization.
Read back deployment state and confirm the delivered application at its public URL.
Keep prebuilt delivery separate from source builds and their dependency graph.
Run local safety checks before requesting credentials or mutating remote state.
Treat a successful CLI exit as incomplete until deployment state and served content are checked.
Share your challenge, scope, and timeline to start a focused conversation.