GitHub Actions
Use the AppBarn CLI in a job after producing the mobile artifact.
Prerequisites
Store APPBARN_TOKEN as a GitHub Actions secret. Store App/Environment UUIDs and Android build identity as non-secret variables or workflow inputs.
yaml
- name: Upload build
env:
APPBARN_TOKEN: ${{ secrets.APPBARN_TOKEN }}
run: |
npm install --global appbarn-cli
appbarn config set api https://api.app-barn.com
appbarn config set app "${{ vars.APPBARN_APP_ID }}"
appbarn config set environment "${{ vars.APPBARN_ENVIRONMENT_ID }}"
appbarn upload ./build/app.apk --app-identifier "${{ vars.APPBARN_APP_IDENTIFIER }}" --version "${{ vars.APPBARN_VERSION }}" --build-number "${{ vars.APPBARN_BUILD_NUMBER }}"AppBarn detects GitHub Actions provenance from the job environment; do not manually copy bearer credentials into metadata.
AI prompt — Add a GitHub Actions upload (Copilot, Codex, Cursor)
text
Inspect the mobile build workflow. After the real IPA/APK/AAB is produced, install appbarn-cli, configure https://api.app-barn.com and actual App/Environment UUIDs, then upload that artifact. Read APPBARN_TOKEN from a GitHub Actions secret; use non-secret variables for target IDs and required Android identity fields. Preserve the workflow and native CI provenance. Never log credentials or invent artifact paths. Ask about ambiguous jobs, targets or missing secret setup, validate YAML and report required settings.Common failures
Use a scoped Automation Token, ensure the artifact exists before this step, and keep the token masked as a GitHub secret.