Pipelines

Settings → Pipelines. A pipeline is a recipe in your repo. CapWrapp starts it; GitHub runs it.

Install

Install TestFlight + Play pipeline writes the workflow on the default branch, from Settings or from Upload for testing when the pipeline is missing. GitHub can only dispatch a workflow that already exists there.

If an old placeholder workflow is present (it fails on purpose), replace it from this screen.

What the recipe does

At a high level: check out the SHA you picked → install JS dependencies → inject secrets → build the website → copy it into Capacitor → on a Mac, archive iOS and upload TestFlight → on Linux, sign an Android bundle and upload Play Internal. Full sequence: What happens during a build.

Store keys are not written into Git. The job asks CapWrapp for them.

Workflow filenames

You can rename files, then save:

• Native workflow — default capwrapp-native.yml
• Preview workflow — default capwrapp-preview.yml (optional)

CapWrapp dispatches those names. If you hand-write a different Actions file, point Settings at it. It must accept workflow_dispatch inputs including sha and version.

Reinstall

Safe to run again if helpers are outdated. It refreshes the .capwrapp/ files and workflow YAML.