Airlock
Concepts

Push Requests

The unit of review in Airlock — lifecycle, contents, and how to manage them.

A Push Request is created every time you push to a gate repo. It's the unit of review in Airlock — similar to a pull request, but it exists locally and is resolved before code reaches the remote.

Lifecycle

A Push Request moves through these states:

  1. Created — Push received by the gate repo
  2. Running — Workflow is executing (lint, test, describe, etc.)
  3. Awaiting Approval — Workflow completed, waiting for human review
  4. Approved — You approved it; code is pushed to the bypass-airlock remote and a PR is created
  5. Canceled — You canceled it; nothing is pushed

If a workflow step fails, the Push Request stops at Running with an error. You can inspect the failure in the Activity tab and either cancel the Push Request or retry the failed job. Retrying resets the failed job and all its downstream dependents back to Pending and re-executes from that point.

What a Push Request Contains

Each Push Request collects artifacts produced by workflow steps:

  • Content — Auto-generated PR summary, walk-through, test results and so on
  • Code review comments — Inline comments on specific files and lines
  • Patches — Suggested fixes

Desktop App Tabs

The desktop app shows each Push Request with four tabs:

TabContents
OverviewGenerated title, description, branch info, overall status
ChangesFull diff with inline AI-generated review comments
PatchesSuggested fixes you can accept or reject individually
ActivityReal-time step execution log with timing and output

The Overview tab shows a generated description along with content artifacts like architecture diagrams, rebase results, and test summaries:

Overview tab showing a generated description and architecture diagram

Rebase results include automatic merge conflict resolution:

Overview tab showing a successful rebase with merge conflict resolution

Test results are presented in a clear summary with per-suite breakdowns:

Overview tab showing test results with 247 tests passing

The Critique tab surfaces inline code review comments with severity levels — from critical security issues to positive reinforcement:

Critique tab showing inline code review comments

CLI Commands

You can list, inspect, and cancel Push Requests from the terminal with airlock runs, airlock show, and airlock cancel.

  • Workflows — Define what runs for each Push Request
  • Artifacts — How steps produce content, comments, and patches