Get started with EAS Workflows

Learn how to use EAS Workflows to automate your React Native CI/CD development and release processes.

Builds, submissions, updates, and more are all a part of delivering your app to users. EAS Workflows consist of a sequence of jobs, which help you and your team get things done. With workflows, you can build your project, run end-to-end tests, submit that build to the app stores, and then run custom scripts after the submission is complete. Since each job can have prerequisites and conditionals, you can automate your and your team's CI/CD for your React Native project.

Get started

Learn what EAS Workflows are and how to use them to automate your CI/CD processes with the following video tutorial:

Watch: Get Started with EAS Workflows

Learn how to automate some of the most common processes that every app development team must tackle: creating development builds, publishing preview updates, and deploying to production.

Share the following slide in your next team meeting to discuss what EAS Workflows are and how they can help your team:

EAS Workflows CI/CD sync slide

Learn the benefits of using EAS Workflows to automate your CI/CD processes.

Set up your project

If you haven't already, you'll need to create a project and sync it with EAS:

Configure your project

EAS Workflows require a GitHub repository that's linked to your EAS project to run. You can link a GitHub repo to your EAS project with the following steps:

• Navigate to your project's GitHub settings.
• Follow the UI to install the GitHub app.
• Select the GitHub repository that matches the Expo project and connect it.

Write a workflow

First, create a directory named .eas/workflows at the root of your project with a YAML file inside of it. For example: .eas/workflows/hello-world.yml.

Now we're ready to write the contents of hello-world.yml. Each workflow consists of three top-level elements:

• name: defines the name of the workflow. For example: "Hello World"
• on: defines when this workflow should be triggered. For example, when pushing a new commit to a GitHub branch.
• jobs: a sequence of jobs which can depend on and pass data between each other. For example: a job that runs a unit test followed by a job that builds your project into an app.

Here's an example of a workflow that prints "Hello, world":

name: Hello World

on:
  push:
    branches: ['*']

jobs:
  Hello World:
    steps:
      - run: echo "Hello, World"

Here's another example that creates and submits an iOS build of a project on every push to every branch. This is similar to running eas build --platform ios --profile production --auto-submit:

name: Release iOS app

on:
  push:
    branches: ['*']

jobs:
  build:
    type: build
    params:
      platform: ios
      profile: production
  submit:
    needs: [build]
    type: submit
    params:
      build_id: ${{ needs.build.outputs.build_id }}

Download the Expo Tools VS Code extension to get descriptions and autocompletions for your workflow files.

Run your workflow

Once you have a workflow file and your project is connected to Expo's GitHub app, you can trigger your workflow by pushing a commit to your GitHub repository. For the workflow to run, you'll need to make sure the trigger (defined with on) you defined in your workflow is met.

Alternatively, you can trigger a workflow manually by running the following command:

Once you do, you can see your workflow running on your project's workflows page.

Got feedback or feature requests? Send us an email at workflows@expo.dev.