GitHub Actions

To ship every commit from GitHub Actions, a workflow on push to main builds the app and runs the release action with two repository secrets. The hotcodepush-team/release-action step wraps the pinned HotCodePush CLI and masks the token and the key. Its inputs are the flags of release create under the same names.

Ship every commit has the prerequisites and the three disciplines. This page carries the GitHub Actions file.

Secrets to setCopy Anchor Link

Both live under the repository's Settings › Secrets and variables › Actions. A job that names environment: production reads them from a GitHub Environment of that name instead, which keeps the key to the jobs you put there.

A pull request from a fork gets no secrets. In a pull request job that releases, such as the preview workflow, guard the job with if: github.event.pull_request.head.repo.full_name == github.repository when the repository takes outside contributions.

The workflowCopy Anchor Link

name: Release to production
on:
  push:
    branches: [main]
jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - name: Check out the commit
        uses: actions/checkout@v7
      - name: Build the web app
        run: npm ci && npm run build
      - name: Release to production
        uses: hotcodepush-team/release-action@v0.1.0
        with:
          token: ${{ secrets.HOTCODEPUSH_TOKEN }}
          private-key: ${{ secrets.HOTCODEPUSH_SIGNING_KEY }}
          channel: production

• A React Native or Expo app replaces the build step with npm ci alone: the CLI packages the bundle per platform inside the upload. A Cordova app whose www is written by hand has no build step either.
• The runner's Node.js must be 22 or later, and GitHub-hosted runners ship it.

The release step logs one line per release and writes a job summary: channel, number, bundle and rollout. A failed release fails the step with the CLI's exit code and an annotation titled with the code, and the error catalog names the fix. A green job and a device that did not take the release is the other case. See Troubleshooting.

A preview channel per pull request runs from the same pipeline, with a QR code in a pull request comment. Test with preview channels has that workflow.

Next stepsCopy Anchor Link

• Ship every commit names the three disciplines a pipeline that ships every commit keeps.
• Test with preview channels has the preview workflow and the tester build that follows a channel.
• Roll out gradually sets rollout-percent and progression on the action and explains the auto-pause counters.