Deploy from GitHub

Infralane can build an application from a repository selected through the workspace’s GitHub connection or from a public Git repository URL.

Connect a GitHub account

For repositories that are not public, open Workspace → Integrations and select the action to install or connect the Infralane GitHub App. GitHub opens in a separate window so you can choose the account and repository access.

Grant access only to the repositories the workspace needs. After returning to Infralane, verify that the integration is shown as Connected for the correct workspace.

A GitHub connection belongs to the current workspace. Switching workspaces can change which repositories are available.

Create the application

Choose Git repository

From Applications → Deploy application, enter the permanent application name and optional description. Keep Git repository selected.

Select repository access mode

Choose Connected GitHub account to search repositories available through the workspace integration. Choose Public Git URL when the repository can be read without a connected account.

Select the repository and branch

For a connected account, search by owner or repository name. Disabled repositories cannot be selected. Confirm the branch; the selected repository’s default branch may be used initially, but you should verify it before deploying.

For a public repository, paste its full HTTPS URL and enter the branch.

Set the root directory

Use / when the application is at the repository root. For a monorepo, enter the directory containing that application’s manifest and build files, such as /apps/web.

Configure the build

Choose Node.js, Python or Go for a source application, or Plain HTML/CSS/JS for ready-to-serve static files. Static builds use Node.js or plain files. Verify the build command, start command or publish directory, and container port. Defaults may not match your project. Git source builds require an amd64 server.

Review and deploy

Choose a resource pool, CPU, and memory. Add runtime values and volumes, review the full summary, then select Deploy application.

Repository troubleshooting

Repository is missing: refresh the list, confirm the workspace connection, and verify that the GitHub App has access to that repository.
Wrong branch: enter an existing branch and check spelling and capitalization.
Monorepo build cannot find files: verify the root directory.
Private dependency cannot be fetched: confirm that your application’s dependency access is configured through a supported, secret-safe mechanism. Never place a token directly in the repository URL or build command.
Archived or disabled repository: choose an active repository or restore access in GitHub before retrying.

Deploy on a GitHub push

A valid push from the connected workspace GitHub installation to the application’s configured repository and branch queues a deployment. Tags, deleted branches and pushes to other branches do not trigger this path. It depends on the installation remaining active and the application still matching that source.

A public Git URL alone does not create a GitHub installation or webhook connection. Check Deployments after a push; do not assume source changes are live until the deployment succeeds. Rapid pushes can produce separate deployment jobs.

Changing source later

Open Settings → Source and build. Saving this section starts a new deployment. Review the new release immediately and keep the previous known-good configuration available in your version-control history.