BlinkHost
BlinkHost
Dashboard
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-08-17

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.

Help improve this page

Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.