GitHub PR preview

Let pull requests trigger inspectable preview deployments.

PR preview requires an explicit user-authored workflow. Appaloft makes the deploy path, preview URL, status, logs, cleanup, and recovery guidance traceable instead of silently changing repository policy.

GitHub Action deploy AI agent entry CLI deploy

PR preview workflow sketch

on:
  pull_request:
    types: [opened, synchronize, reopened]
jobs:
  preview:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: appaloft/deploy-action@v1
        with:
          preview: true
          config: appaloft.yml

Entrypoint

GitHub Actions

Trigger

pull_request

Secrets

GitHub Secrets

Cleanup

close workflow

Output

preview URL + status

The preview workflow must explicitly subscribe to pull_request events

Close cleanup uses a separate workflow so preview environments do not linger

When secrets are needed, reference GitHub Secrets names instead of printing values

Workflow boundary

PR preview is not an implicit default behavior. The repository declares triggers, permissions, secrets, and target deployment path.

Status feedback

On success, return preview URL, deployment id, and check status. On failure, return logs and diagnostics instead of presenting a failed preview as successful.

Cleanup policy

PR close or merge should trigger a cleanup workflow. If cleanup fails, report the manual cleanup gap clearly.

Deployment flow

Add preview workflow

Declare a pull_request-triggered deployment workflow in the repository.

Configure secrets

Store SSH key, server, token, and related credentials in GitHub Secrets.

Add cleanup workflow

Create a separate cleanup path for pull_request close events.

Keep following the same deploy path.

Appaloft SEO pages are organized around real deployment tasks. Each page should lead to the next useful step, not stand alone.

GitHub deployment

Use GitHub Actions to connect repository events to Appaloft deployment while keeping explicit workflows.

AI deployment

Let the agent identify project shape first, then choose the skill, CLI, static publishing, or Cloud console path.

Own server deployment

Tie the control plane, CLI, servers, rollback, and Cloud collaboration boundary into one self-hosting cluster.

Static site publishing

Connect build output, browser upload, CLI deploy, and one-click buttons for static site publishing.