Review Workflow

The Review Queue is the heart of Reshot's governance model. Just like code needs a Pull Request, visual changes need review before they replace the current approved image.

How Items Enter the Queue

Every time you run reshot publish:

Asset StatusQueue StatusAction Required
New VisualsPENDINGNeeds approval
Changed VisualsPENDINGNeeds approval
Unchanged VisualsAPPROVEDNone (auto-approved)

Reviewing Changes

Navigate to CLI Commits in your project dashboard.

Filter Views

  • All Visuals: Complete gallery
  • Pending Reviews: Items awaiting approval
  • Recently Changed: Last 7 days of activity

Actions

ActionIconResult
ApproveStable URLs start serving the approved version
RejectChange is discarded, previous approved version remains

Approval Flow

  1. Developer runs reshot publish locally or in CI
  2. Changed assets appear in Review Queue
  3. Team member reviews changes (with diff overlay)
  4. Approves or rejects each visual
  5. Approved visuals make the stable CDN URL serve the new image
CLI Commits Review Queue
The CLI Commits queue shows pending publishes, affected visual counts, and approval actions before the approved image replaces the current one

Bulk Actions

For large batches:

  • Approve All: Accept all pending changes at once
  • Filter & Approve: Approve by scenario or variant

Review Permissions

RoleCan Review
Owner
Member
Viewer
Review Workflow — Reshot Docs | Reshot