ZelaresZelares

Import a project from GitHub

Workspace owners and administrators can connect an approved GitHub App installation and import a repository snapshot into a new Zelares project. This is separate from using GitHub to sign in to Zelares.

Connect GitHub

  1. Open a workspace's Projects page.
  2. Choose Import from GitHub.
  3. Choose Connect GitHub and complete the GitHub App authorization. If your GitHub account has multiple authorized installations, choose the installation for this Workspace when Zelares asks.
  4. Return to Zelares and refresh the repository list if the installation was changed.

Only repositories granted to the selected GitHub App installation are listed. Zelares does not ask you to paste a personal access token into the browser.

Import a repository

  1. Enter the title for the new Zelares project.
  2. Select a repository that the GitHub App can access.
  3. Enter a branch or ref. The import records the resolved commit used for the snapshot.
  4. Optionally enter a repository-relative root path such as docs.
  5. Choose Import project and wait for the project import to finish.

Zelares reuses the normal project-import lifecycle, including project permissions, quotas, supported file limits, storage handling, retryable cleanup, and recovery for interrupted imports. Generated directories such as .git, node_modules, .next, and dist are skipped.

Current limits

  • The GitHub App integration must be configured by the Zelares operator before a workspace can connect it.
  • This release imports a snapshot and records its source repository, ref, commit, installation, and root path.
  • GitHub webhook auto-updates, conflict resolution for simultaneous edits, and pushing Zelares changes back to GitHub are not available yet.
  • Provider, browser, MongoDB, and storage failures are reported as recoverable errors; retry repository discovery before reconnecting when the Workspace is still shown as connected, and do not retry a failed import blindly if the UI reports cleanup is still pending.
  • Symbolic links are not supported in a GitHub snapshot and are rejected rather than imported as regular-file contents.
  • Repository paths containing literal backslashes are rejected because GitHub uses / for hierarchy and Zelares does not reinterpret a provider filename.

Related help