GitHub Actions

Set up

Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher

2. Navigate to App Settings by clicking the gear icon (⚙️) at the top of the Timeline sidebar

3. Click on Integrations in the sidebar

Connect GitHub Actions

• Find the GitHub Actions integration module under the CI/CD section

• Click the Connect button. You’ll be taken through a standard GitHub app OAuth flow. (Or, you’ll be given the option to reuse the GitHub connection you already established when setting up GitHub for version control.)

• GitHub redirects you back to Runway

  • Select the name of your repo from the list of options

  • Select the name of your Release Candidate workflow from the list of options

  • Optionally, enter the name of your release workflow (the one that generates the builds that you end up submitting to the App Store/Play Store) if it’s different than your Release Candidate workflow

  • Optionally, enter the name of the deploy branch on which your release workflows are triggered, if this branch is different than the branch your Release Candidate workflow is triggered on

Learn more about builds and branches in Runway.

Triggering workflows from Runway

The generated build-and-deploy workflow is by default configured to be manually triggered from GitHub Actions by choosing a branch. But you can also include event triggers to automatically run your workflow on pushes to a specific branch.

We recommend including an automatic event trigger for your workflow so that it runs on pushes to any release branches like so:

on:
  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:
  # Triggers the workflow on push to release branches
  push:
    branches:
      - "releases-{**}"

You can read more about available event triggers in GitHub’s documentation.

nabl artifact downloads