Connect and import a GitHub repository

Connect GitHub

Open Project settings → Source control. Choose Connect for deploys for read-only source access or Connect for collaboration when authorised users must push explicit IDE commits. In GitHub, select only the account and repositories BlinkHost needs.

Import source

1. Choose a repository and branch or full commit SHA.
2. Enter . for a root application or a normalized path such as apps/web for a monorepo.
3. Choose deploy-only or two-way sync.
4. Review the detected framework, package manager, build command and output directory.
5. Import the exact resolved commit.

BlinkHost rejects traversal, links, device files, duplicate or case-colliding paths, decompression bombs and repositories outside published bounds. UTF-8 source enters the editor. Binary files are listed for an explicit Project Assets import so they pass the asset security lifecycle and shared-storage accounting.

Folders under _server_islands are only candidates. Create or link each Rust, Go or Python module through Backend Modules so the ABI, SDK, compiler and artifact lifecycle remain verified.

Work safely

Pull uses a three-way comparison between the last shared commit, the saved IDE workspace and the current branch. Conflicting paths are shown without overwriting the workspace. Push compares the expected old commit before advancing the branch; pull and resolve when it changed.

Share a BlinkHost project with GitHub

You can also start in BlinkHost and share the complete project to GitHub:

1. Create an empty GitHub repository. Do not add a README, licence or .gitignore during creation.
2. Return to Project settings → Source control and refresh the repository list.
3. Select the repository, choose the initial branch and review the commit message.
4. Choose Share project.

The first commit contains the frontend workspace, registered backend-module source, database schema and migration files, validated Project Assets, starter READMEs and blinkhost.yaml. Secret values, database credentials, production data, build output and local runtime state are never exported.

BlinkHost will not replace existing repository history. If the first export was interrupted after GitHub accepted only part of the exact project tree, repeat the action to finish it safely. If the repository contains any other content, import and review that repository instead.

Project Assets are included only after their upload and integrity checks complete. A new or changed binary arriving from GitHub must be imported through Project Assets before a pull can update the workspace.