Quick Start Guide

Welcome to the official documentation for the SwapLab Private Builder. This guide will walk you through the absolute prerequisites required before you can trigger a build from the UI.

The Digital Bridge Model

Unlike the public service, private.swaplab.net acts only as a secure trigger. All code compilation and processing occur on your own GitHub Action runners. Therefore, you must prepare a dedicated private repository to host the workflow files.

Prerequisites & Setup

Create a Private Repository

Log in to your personal or organizational GitHub account and create a new repository. It must be set to Private. Public repositories will be strictly rejected by our server.

Create the Required Workflow Files

Inside your new private repository, you must create a specific directory structure: .github/workflows/. Inside this folder, you must place our pre-configured YAML files.

CRITICAL: The file names and their contents must match exactly. If you alter the file names or the YAML structure, the SwapLab backend will fail to execute the workflow.

Required Files (Copy contents directly from these links):

swaplab-workflow-cache.yml (Recommended for faster builds)
swaplab-workflow-no-cache.yml (For clean builds)

Your Repository Structure should look exactly like this:

my-private-app-repo/
├── .github/
│   └── workflows/
│       ├── swaplab-workflow-cache.yml
│       └── swaplab-workflow-no-cache.yml
├── src/
├── package.json
└── ...

Connect via the UI

Once your private repository is set up with the workflow files, return to private.swaplab.net and Sign In.

In the Target Action Repository URL field, paste the full URL of your new repository. For example:

https://github.com/your-username/my-private-app-repo

Note on Release Builds

If you intend to compile a Release APK or AAB, you must also add your Base64-encoded keystore to this repository's GitHub Secrets under the exact name KEYSTORE_BASE64. You can generate this base64 string securely via keystore.swaplab.net.