OverviewGaFor developerFor agencyFor operatorFor evaluator

Git source control on BlinkHost

Choose what Git owns, what BlinkHost owns, and how browser drafts become intentional commits and verified releases.

Last updated 2026-09-02

What you'll achieve

Understand the boundary between Git history and BlinkHost runtime state
Choose deploy-only or explicit two-way synchronization
Deploy without adding GitHub Actions to a customer repository

The ownership boundary

GitHub is authoritative for committed source and history. BlinkHost is authoritative for private browser drafts, project resources, secret values, database instances, runtime policy, plan entitlements, verified build artifacts and deployments.

Browser autosave never creates a commit. Choose Commit and push when a saved IDE draft should become Git history. A push or pull from GitHub never creates a database, secret or backend module merely because a folder or manifest entry exists; approve those resources in BlinkHost.

Build locations

Interactive frontend editing, preview and builds continue to run in the WebContainer on your device. Rust, Go and Python backend modules always use the BlinkHost trusted compiler. A repository push, pull request or merge queue cannot use your browser, so its frontend build runs in a BlinkHost-managed isolated builder against one immutable commit.

GitHub Actions is optional. BlinkHost's GitHub App receives selected repository events, reports checks and uses short-lived installation tokens on the server.

Connection modes

Deploy-only: read committed source and build previews or releases.
Collaborate: adds explicit pull, commit and branch-update operations. It never exports secrets or resource credentials.

GitHub sign-in and GitHub repository authorization are separate. Signing in with GitHub does not grant BlinkHost access to a repository.

Start a project from its source

Choose Import from GitHub when the code already exists, Start with a framework for a maintained browser starter, Use a verified template for repeatable team delivery, or Start with HTML for a lightweight project without dependency installation. A new project remains a private draft until you publish it.

Repository import opens Source settings first so you can authorize the repository, review the detected frontend and backend directories, confirm the production branch and see compatibility findings before source is replaced. A starter or HTML project opens directly in the browser IDE. You can connect GitHub later without changing the project URL.

Use the project overview to follow the delivery path from source through LiveStack Preview and release checks to production. It reports the current state and one recommended next action; it does not treat a connected repository, a successful preview or a saved file as a production release.

Move between projects and tools

The workspace switcher remains available while you are inside a project. Project navigation groups build, service, delivery, observability and configuration tools. Press Ctrl+K or Command+K outside the IDE to search projects and open common actions without leaving the current workspace.