Skip to main content
GitHub deployment requires Pro and a configured GitHub integration. If the App says the integration is not enabled, the operator must enable it before this flow is available. GitHub sign-in alone does not grant repository access.
First connect an Engine and complete its deployment prerequisites. Your repository must be deployable by the Engine, and required application secrets must already be set on the machine.
1

Connect the GitHub App

Open GitHub integration. Install the Nerdit GitHub App on the relevant GitHub account or organization and select the repositories it may access.
2

Choose machine access

Return to the GitHub page and review Machine access. Select the repositories the destination machine may clone. Keep this selection limited to the repositories that machine needs.
3

Open deployment

From the machine page, select Deploy from GitHub. Choose a repository and an online machine. If the repository is missing, review its GitHub App installation and the machine’s repository access.
4

Set the deployment options

Enter a Service name using lowercase letters, digits, and dashes, between 1 and 63 characters. Set Branch or tag, or leave it blank for the default branch. Enable Auto-deploy on push only if you want pushes to the branch to redeploy the app.
5

Choose and inspect the build

Choose Node.js, Next.js, Python or Dockerfile in Build preset, or keep the saved/repository setting. Auto-detect clears a saved preset. Expand Build settings for commands, runtime, package manager and root directory, then select Inspect build. After edits, select Inspect again to refresh the preview; inspection is optional and does not compile the app. These controls require an Engine with build-settings support.
6

Deploy and inspect the result

Submit the deployment. Review the returned outcome and hints, then follow the machine link to monitor the app. A started deployment still needs to finish building and become healthy.
Build commands are saved configuration: never paste credentials into them. Build-time public variables are supported on Engine 0.6.2 and later through the Public variables section; their values are embedded in the browser bundle, so never put a secret there. Secret mounts at build time are not supported. See build overrides. Missing-secret warnings list names only. Set required values on the machine; the App does not edit them. For build failures, use the Engine’s diagnostics and App troubleshooting. Later, use Redeploy or Roll back from the app’s menu when available. See Manage applications for their limits.