UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Integrations

GitHub integration

What the GitHub integration does in Ulika, where it shows up in your project, and links to the detailed connection and permission guides.

Last updated October 10, 2026

GitHub is where your site's code lives, and it is the one integration every Ulika project depends on. Ulika connects to GitHub through a GitHub App so it can read your repository, add its connector through a pull request, and publish your content. This page is the overview. The detailed guides are linked below.

What the integration does#

  • Reads your repository. Ulika reads the repository at one commit, in memory, to find editable text, images and links. Your source code is never stored.

  • Adds the connector. It creates a branch and opens a pull request that you review. See Approving a connection.

  • Publishes your content. When you publish, Ulika commits one content file to your default branch, or opens a pull request if the branch is protected. See Publish.

  • Reads your host's build results. With read-only access to commit statuses, checks and deployments, Ulika can confirm that your host built a preview or a production deployment. See Private previews.

How it appears in the product#

In your project, open Settings and then the Integrations tab. GitHub is listed under Source control with this description: "Connects your repository so Ulika can read component source and detect content." It shows Connected when the project has a connected repository, and otherwise it does not. That status says the project is tied to a repository; it is not a live health check of Ulika's access. For the repository itself, use the Repository tab.

The Repository tab shows:

  • the repository name as owner/name, with a Connected or Disconnected badge,

  • the branch, the provider, and what the site was built with, when known,

  • when the project was last synced and when the last GitHub event arrived,

  • a Change repository button (for people who can edit settings) and an Open repo link.

Changing the repository replaces the imported content and is blocked while the site is live through Ulika. See Connect from the dashboard.

Setup in one minute#

  1. In the dashboard click Connect website, check your site, then choose Connect with GitHub.

  2. Install the Ulika GitHub App on the account that owns the repository, and select the repository.

  3. Pick the repository in Ulika and turn on live editing.

The full walk-through is in Connect from the dashboard. If you prefer a terminal or an agent, the same GitHub connection is used behind the scenes by the CLI and AI agents.

What the app can and cannot do#

The app asks for read access to your repository's contents and metadata, write access to contents and pull requests, and read-only access to statuses, checks and deployments. It never writes the connector to your default branch, never force-pushes, and never merges a commit it did not write. The full table, and how to accept permission updates, is in The GitHub App.

Rules to keep in mind#

  • A repository can be connected in only one Ulika workspace at a time.

  • Only workspace owners and admins can connect a site. See Roles.

  • Removing the app on GitHub stops Ulika from reading or writing your repository. Connector files already merged stay in your code.

Learn more#

  • The GitHub App: installing, permissions, adding repositories.

  • Connect from the dashboard: the full browser flow.

  • Troubleshooting GitHub: fixes for permission and access problems.

  • Security overview: how Ulika handles your code.

Was this page helpful?

PreviousConnect VercelNext Vercel integration

On this page

  • What the integration does
  • How it appears in the product
  • Setup in one minute
  • What the app can and cannot do
  • Rules to keep in mind
  • Learn more
Ulika documentationFAQ · CLI reference · Terms · Privacy