---
modificationDate: December 03, 2025
title: GitHub Action for PR previews
description: Learn how to use GitHub Actions to automate publishing updates with EAS Update.
---

<AgentInstructions>

## Submitting Feedback

If this page contains errors, outdated information, or gaps that blocked you from completing a task, report it so the docs can be improved:

curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas-update/github-actions/","feedback":"🤖 Agent feedback: <specific, actionable description>"}'

Only submit when you have something specific and actionable to report.

</AgentInstructions>

# GitHub Action for PR previews

Learn how to use GitHub Actions to automate publishing updates with EAS Update.

> For the complete documentation index, see [llms.txt](/llms.txt). Use this file to discover all available pages.

A GitHub Action is a cloud function that runs every time an event on GitHub occurs. You can configure GitHub Actions to automate building and publishing updates when you or members of your team merge to a branch, like "production". This makes the process of deploying consistent and fast, leaving you more time to develop your app.

This guide will walk you through how to set up GitHub Actions to publish previews on pull requests.

## Publish previews on pull requests

Another common use case is to create a new update for every pull request. This allows you to test the changes in the pull request on a device before merging the code, and without having to start the project locally. Below are the steps to publish an update every time a pull request is opened:

Create a file path named **.github/workflows/preview.yml** at the root of your project.

Inside **preview.yml**, copy and paste the following snippet:

```yaml
name: preview
on: pull_request

jobs:
  update:
    name: EAS Update
    runs-on: ubuntu-latest
    permissions:
      contents: read
      pull-requests: write
    steps:
      - name: Check for EXPO_TOKEN
        run: |
          if [ -z "${{ secrets.EXPO_TOKEN }}" ]; then
            echo "You must provide an EXPO_TOKEN secret linked to this project's Expo account in this repo's secrets. Learn more: https://docs.expo.dev/eas-update/github-actions"
            exit 1
          fi

      - name: Checkout repository
        uses: actions/checkout@v5

      - name: Setup Node
        uses: actions/setup-node@v6
        with:
          node-version: 22
          cache: yarn

      - name: Setup EAS
        uses: expo/expo-github-action@v8
        with:
          eas-version: latest
          token: ${{ secrets.EXPO_TOKEN }}

      - name: Install dependencies
        run: yarn install

      - name: Create preview
        uses: expo/expo-github-action/preview@v8
        with:
          command: eas update --auto
```

In the above script:

-   You are using the workflow event `on` to run every time a pull request is opened or updated.
-   In the `update` job, the Node.js version, Expo's GitHub Action and the dependencies are set up using GitHub Action's built-in cache.
-   The `eas update --auto` is run by the [preview subaction](https://github.com/expo/expo-github-action/tree/main/preview#readme). It adds a comment to the pull request with basic information about the update and a QR code to scan the update.

> Don't forget to add the `permissions` section to the job. This enables the job to add comments to the pull request.

You can skip this step if you have already set up `EXPO_TOKEN` in the previous section. Only one valid `EXPO_TOKEN` is required to authenticate GitHub Actions with your Expo account.

If you haven't, you need to give the script above permission to run by providing an `EXPO_TOKEN` environment variable.

-   Navigate to [https://expo.dev/settings/access-tokens](https://expo.dev/settings/access-tokens).
-   Click **Create token** to create a new personal access token.
-   Copy the token generated.
-   Navigate to [https://github.com/your-username/your-repo-name/settings/secrets/actions](https://github.com/your-username/your-repo-name/settings/secrets/actions) by replacing "your-username" and "your-repo-name" with your project's info.
-   Under **Repository secrets**, click **New repository secret**.
-   Create a secret with the name **EXPO_TOKEN**, and paste the copied access token in as the value.

Your GitHub Action should be set up now. Whenever a developer creates a pull request, this action will build an update and publish it, making it available to all reviewers with builds that have access to the EAS branch.

> Some repositories or organizations might need to explicitly enable GitHub Workflows and allow third-party Actions.

## Using Bun instead of Yarn

To use [Bun](/guides/using-bun) as the package manager instead of Yarn, follow the steps below for both publishing updates on push and previews on pull requests:

Replace the `Setup Node` step in **update.yml** or **preview.yml** with the following snippet:

```yaml
- name: Setup Bun
  uses: oven-sh/setup-bun@v1
  with:
    bun-version: latest
```

To install dependencies using Bun, replace the **Install dependencies** step with the following snippet:

```yaml
- name: Install dependencies
  run: bun install
```