Before you import
You need an Ocacity account, access to the GitHub repository and an available GitHub connection in Ocacity. Signing in to Ocacity with GitHub is separate from granting access to repositories. An organisation may also require its owner to approve the connection.
The import creates a source snapshot from the repository’s default branch. It records the commit used and opens a new project in the editor. Your existing Ocacity project is saved before switching, and the GitHub repository is not changed by importing it.
1. Open Import from GitHub
In the workspace, open the + menu beside the prompt and select Import from GitHub. If your account is already connected, the dialog loads the repositories available to that connection.
For a new connection, select Continue with GitHub and complete the authorisation on GitHub. When you return to Ocacity, the import dialog lets you choose a repository. If the dialog says the GitHub connection is coming online, the site’s GitHub App still needs to be configured.
2. Choose repository access
If no repositories are available, use Choose repository access to install or configure the Ocacity GitHub App on the repositories you want to use. Return to the import dialog and select Refresh access after changing permissions.
The app requests code and pull-request access to support reviewed changes. You choose its repository access on GitHub. If you have more than one personal or organisation installation, use the account buttons in the dialog to switch between them.
3. Find and select your repository
The dialog shows the most recently updated repositories first, with ten visible initially. Search by repository name or description, or select Show more repositories to reveal another ten. Each row identifies the repository owner, whether it is private, and its default branch.
Select a repository row to import it. Ocacity reads a single commit from its default branch, saves the supported files as a new project and opens the code editor. The import summary identifies the repository, branch and commit, and lists excluded file categories.
For very large GitHub accounts, the list is bounded to the first 2,000 accessible repositories for the selected installation. If the dialog reports that limit, narrow the app’s repository access on GitHub and refresh access.
What is included in the import?
Browser import is designed for a small source project. It accepts up to 80 source files, with a 120 KB limit per file and a 500 KB limit for the stored source project, including its structure. A repository exceeding those limits is rejected rather than silently cut down to a partial set of source files.
- Supported text source is copied into the editor, including files such as HTML, CSS, JavaScript, TypeScript and project configuration.
- Credential paths, including environment files and private-key files, are excluded.
- Dependency and generated folders, such as
node_modules,distand.next, and package lockfiles are excluded. - Binary assets, symbolic links and Git submodules are excluded. Local images, fonts or other omitted assets may need a separate supported source before a preview is complete.
Some repository paths and file encodings cannot be stored by the browser editor. If the import reports an unsupported path or an oversized project, use a smaller source repository or work with the full repository locally. Keep the original repository as the complete source of the project.
4. Review the source and choose how to run it
Start with the import summary and file tree. Check the entry file, package configuration and any references to assets or environment variables. Importing source does not install dependencies or run runtime checks.
Use the browser preview for a supported frontend project. A project requiring a development server needs the appropriate local preview connection or configured execution environment. The Ocacity feature overview explains the available workflows.
Then ask for one concrete change. For example: “In the existing mobile navigation, keep the current colours and links, but fix the menu so it closes after selecting a page. Explain the files changed and how to test it.” Review the resulting source and test the affected behaviour.
Importing is a snapshot, not continuous GitHub synchronisation. Edits in the Ocacity project do not automatically become GitHub commits. A GitHub change needs its own reviewed submission; importing does not create a pull request, merge code or deploy the project.
If a repository is missing or the import stops
- Wrong account: check the connected GitHub login and the selected account in the dialog. Switch to the installation that owns the repository.
- Missing access: update Choose repository access, complete any organisation approval, then select Refresh access.
- Expired authorisation: sign in to Ocacity again or reconnect GitHub as directed by the displayed error.
- A task is still running: finish or stop it and save your current changes before importing another project.
- Source limits or no supported files: read the reported limit and compare it with the files above. A repository containing only excluded assets has no source to import.
You can disconnect GitHub from the same dialog. Repository permissions can also be changed in GitHub’s application settings. Disconnecting does not delete the project source you already imported.