Target Action Repository URL

This input field requires the exact URL of the GitHub repository that will act as the host for your Action runners. The SwapLab Engine uses this URL to dispatch the build commands directly to your private infrastructure.

Visibility: The repository must be set to Private. Public repositories will be automatically rejected.
Installation: The SwapLab Engine GitHub App must be authorized for this specific repository.
Format: Enter the full URL (e.g., https://github.com/username/my-private-app).

How it Relates to "Project Source Code"

The role of your Target Repository changes significantly depending on the Project Source Code option you select in the UI. Please review the two scenarios below carefully.

folder_zip Scenario A: You select "Upload .zip"

If you choose to upload or drag-and-drop a .zip file of your project from your local computer, the Target Repository acts only as a runner host.

Your Target Repository does not need to contain your app's source code or assets.
It only needs to contain the required YAML workflow files (e.g., .github/workflows/swaplab-workflow-cache.yml).

Data Lifecycle: Your uploaded ZIP is sent to temporary secure storage (R2). As soon as the runner starts, it downloads and extracts the ZIP into RAM, and immediately requests the permanent deletion of the ZIP from R2 before the build even begins.

code Scenario B: You select "Use Repository"

If you choose the "Use Repository" option, you are telling the builder to pull the source code directly from GitHub.

Your Target Repository must contain your entire application's source code (like package.json, src/, etc.) located at the root of the repository.
It must also contain the required YAML workflow files in the .github/workflows/ directory.
The build will be executed based on the latest commit in your repository's default branch.

Data Lifecycle: With this option, no source code is uploaded from your browser. The runner pulls the code directly from your private GitHub repository.

Final Build Artifacts Lifecycle

Regardless of whether you choose Scenario A or Scenario B, and regardless of whether the build succeeds or fails, the final output artifacts (such as APK, AAB, Export Android Studio ZIP, or Export Xcode ZIP) are handled with the same strict retention policy:

Artifacts are uploaded to temporary secure storage (R2) to provide a download link.
A strict automated cron job ensures that all output artifacts are permanently deleted after exactly 1 hour.
You can monitor your recent builds in the UI, but the download links will expire and the files will be destroyed after the 60-minute window.