To integrate Shorebird into your CI, use the setup-shorebird action. The
setup-shorebird action downloads Shorebird and adds it to the system path.
name: Shorebird Workflow Exampleon: workflow_dispatch:jobs: example: defaults: run: shell: bash runs-on: ubuntu-latest steps: # Use the setup-shorebird action to configure Shorebird - name: 🐦 Setup Shorebird uses: shorebirdtech/setup-shorebird@v1 with: cache: true # Optionally cache your Shorebird installation # Now we're able to use Shorebird CLI in our workflow - name: 🚀 Use Shorebird run: shorebird --version
In the above workflow, we’re using the setup-shorebird action to configure
Shorebird in our CI and in subsequent steps we can execute any Shorebird
commands.
Most Shorebird functionality, like creating releases and patches, requires
authentication. To authenticate in your CI, create an API key from the
Shorebird Console:
Go to Account → API Keys.
Click Create API Key.
Give the key a name (e.g., “GitHub Actions — my-app”), choose an expiration,
and select a permission level.
Copy the key value — it is only shown once.
Use this key as your SHOREBIRD_TOKEN in CI. The environment variable name is
unchanged from previous versions.
See API Keys for details on permission levels
and other key management options.
Next, copy the generated SHOREBIRD_TOKEN and navigate to your GitHub
repository secrets via:
"Settings" -> "Secrets and variables" -> "Actions".
Then, click "New repository secret" and paste your SHOREBIRD_TOKEN: