Skip to main content
Connect a GitHub repository to an app so Meridian can build and deploy from your source, and so a push can ship a release.

​
Connecting a repository

Install the Meridian GitHub app and connect a repository from the GitHub card in your app’s Settings → Integrations (Manage on the repository card in Hosting opens the same page). The card then names the linked repository: “Connected to owner/repo”. Meridian can read the repository’s branches and recent commits and build from any of them. You can create a brand-new Meridian app directly from a GitHub repository.

​
Deploying from GitHub

With a repository connected:
  • Push to deploy: a push to the connected branch triggers a deployment.
  • PR previews: a pull request gets its own preview deployment at the PR’s head commit, torn down when the PR closes or after seven days without a push. An app keeps at most two live previews. When a third pull request opens, the oldest preview is removed first and its pull request gets a comment saying so. Pushing a new commit to that pull request deploys its preview again. Only pull requests opened from a branch of the connected repository by its owner, an organization member or a collaborator get a preview. Pull requests from forks, and from anyone without write access, never build, because a preview runs the pull request’s code.
  • Manual deploys: pick any commit and deploy it from the dashboard.
Push deployments and PR previews require deployment access from your subscription, just like manual deploys. They are also blocked when the app is locked because its free trial ended, its organization is suspended, or it has no plan while the organization pays for other apps. Meridian checks that access before accepting a GitHub deployment and again before starting its build or runtime deployment. Closing a pull request still cleans up its preview even if deployment access has ended. Meridian always builds the exact commit you selected; a sha that hasn’t been pushed to the connected repository fails during the build rather than silently.

​
Switching or disconnecting

Configure on the GitHub card shows the linked repository first, with Disconnect, and below it the list of accounts to switch to another repository. Disconnecting a repository stops push and PR deploys. Existing running revisions are unaffected until the next deploy. The app keeps serving what it last released.
Last modified on October 6, 2026