CI Runs

⚙️ CI runs list — recent workflow runs with status

Requirements

CI features require a connected GitHub Personal Access Token with repo and workflow scopes. See Onboarding — Step 2 for setup.

The app’s repository must be set in the App Detail view (a “Connect GitHub” row appears if it isn’t).

CI Runs section

The CI Runs section on the App Detail view shows the most recent runs for the app’s linked repository. Each row shows:

Workflow name
Branch
Run status (queued, in progress, success, failure, cancelled)
Triggered time

Tap any run to open the live monitor for that run.

Live run monitor

The run monitor shows:

Current overall status (with a live spinner if the run is in progress)
Each job within the workflow, with its status
Tap a job to expand and read its step-by-step log output in real time

Mainline polls for updates automatically while the sheet is open.

Triggering a workflow

In the App Detail view, tap Trigger Build (or the equivalent button shown in the CI section).
Select the workflow file you want to run (Mainline lists all workflow files in your repo's .github/workflows/ folder that have workflow_dispatch enabled).
Select the branch to run on.
Tap Trigger. Mainline dispatches the workflow via the GitHub API and immediately opens the run monitor for the new run.

💡

Only workflow_dispatch workflows can be triggered

GitHub requires workflows to have on: workflow_dispatch in their YAML to be manually triggered. If no workflows appear in the list, add the workflow_dispatch trigger to your workflow file and push the change.

Cleaning up build artifacts

Mainline includes a Clean Up Builds action that can delete old expired or superseded build records from ASC (not the GitHub run logs). This helps keep the builds list readable when you have many old builds accumulating.