Deploy an application from GitHub

GitHub App access lets Bundar list repositories and branches available to an installation, clone the selected source for a deployment, and deploy when the selected branch receives a push.

Install and connect the GitHub App

In a project's Add application wizard, choose Git / source build, then GitHub App under repository access. If no GitHub integration is connected, choose Connect GitHub. Bundar takes you to GitHub to install the Bundar GitHub App; choose the personal account or organization that owns the repository, then choose which repositories the installation can access. You may need an account owner or organization administrator to install the app or change its repository access.

Complete the GitHub authorization and return to the wizard. Bundar preserves the application draft. Select the connected GitHub account/installation, then choose a repository and branch. The repository list contains only repositories available to that installation; if one is missing, check the installation's account and repository selection in GitHub. Bundar also checks that the signed-in GitHub user can access the installation.

The exact permission labels are presented by GitHub for the Bundar App; they can change independently of the Bundar wizard. Grant access only to the account and repositories you intend to deploy. A repository must be included in the installation for Bundar to read it and offer it here.

Choose the branch and build file

Choose the repository and branch/ref to deploy. Bundar fills in the repository's default branch when available, but the branch/ref is required. A push to the selected branch triggers a deployment.

Dockerfile Path can be left empty to find a Dockerfile or Containerfile at the repository root. If your build file is elsewhere, enter its path relative to the repository root, such as deploy/Dockerfile. If no root build file exists and the path is empty, Auto detect and build container can generate a Dockerfile from the repository; review the build logs and generated file rather than assuming every project will build without changes. Builds run with Podman on the selected server.

Continue through the application settings, set its type and optional environment variables or volumes, then choose a server ready for that type. For web apps, configure the container port and any domain; see Configure a domain. For the overall wizard, see Add an application.

Preview cleanup

When pull-request previews are enabled, closing or merging a pull request queues deletion of its preview application. Bundar cancels its deployment jobs, removes its Caddy route and domain security settings, and removes its service containers before deleting its application and deployment records. The parent application is not deleted.

The server must be reachable for cleanup to finish. If remote cleanup fails, Bundar keeps the preview records and retries the deletion job. Check the deletion notification for failures. Service deletion does not prune cached images or delete persistent volumes, bind-mounted data, or the shared project network. Preview applications do not inherit the parent's volumes.