Fargone integrates with GitHub for seamless deploys. Connect a repo and every push can trigger a build.

How it works

Fargone operates as a GitHub App. When you install it on a repository, the platform receives push events and can clone your code.

Two ways to access repos

1. GitHub App installation — Install the Fargone GitHub App on your org or personal account. This grants the platform access to specific repositories.
2. GitHub SSO — If you linked your GitHub account via SSO (under Settings > Auth), the platform can also list repos using your personal token.

Both sources are merged and deduplicated when you browse repos in the web UI or CLI.

Connect a repo

CLI

fargone apps create my-app --github https://github.com/you/repo

Web

1. Go to Dashboard > Apps > New App.
2. Click From GitHub.
3. Authorize the GitHub App if prompted.
4. Select a repository and branch.
5. Click Create.

Auto-deploy

Enable auto-deploy to trigger a new deployment on every push:

fargone apps create my-app --github https://github.com/you/repo --auto-deploy

Or toggle it in the web UI on the app detail page.

When a push event arrives, the platform finds all apps matching the repo, branch, and auto-deploy flag, then enqueues a build for each.

Branches

You can deploy from any branch. The default is main. Specify a different branch at creation:

fargone apps create my-app --github https://github.com/you/repo --branch develop

The platform lists available branches using the GitHub API (installation token, SSO token, or a global GITHUB_TOKEN as fallback).

Token fallback chain

When cloning a repo, the platform tries these credentials in order:

1. GITHUB_TOKEN environment variable (platform-level).
2. GitHub App installation access token.
3. User's linked GitHub SSO access token.

Private repos require at least one of these to be configured.