You can easily add Cased deploys to your existing automation on GitHub Actions. For example, if you trigger production deploys after a merge to main, you can add a Cased deploy to the end of the workflow. Just hit Cased API with a single request, and Cased will do the rest.

Here’s an example workflow that deploys to Cased after a merge to main, including use of Blacksmith for fast infrastructure.

name: Deploy Application

on:
  pull_request:
    types: [closed]

jobs:
  deploy:
    if: github.event.pull_request.merged == true
    name: Deploy app
    runs-on: blacksmith-4vcpu-ubuntu-2204
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        with:
          ref: ${{ github.event.pull_request.base.ref }}

      - name: Deploy with Cased
        uses: cased/cased-deploy-action@v2
        with:
          branch_name: ${{ github.event.pull_request.base.ref }}
          target: 'prod'
          cased_token: ${{ secrets.CASED_TOKEN }}
Deploy a BranchDeploy intelligence and failure analysis