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 going live.
How Items Enter the Queue
Every time you run reshot publish:
| Asset Status | Queue Status | Action Required |
|---|---|---|
| New Visuals | PENDING | Needs approval |
| Changed Visuals | PENDING | Needs approval |
| Unchanged Visuals | APPROVED | None (auto-approved) |
Reviewing Changes
Navigate to Visuals in your project dashboard.
Filter Views
- All Visuals: Complete gallery
- Pending Reviews: Items awaiting approval
- Recently Changed: Last 7 days of activity
Actions
| Action | Icon | Result |
|---|---|---|
| Approve | ✓ | New version goes live immediately |
| Reject | ✗ | Change is discarded, previous version remains live |
Approval Flow
- Developer runs
reshot publishlocally or in CI - Changed assets appear in Review Queue
- Team member reviews changes (with diff overlay)
- Approves or rejects each visual
- Approved visuals update live CDN URLs instantly
1
View Pending Commits
Navigate to CLI Commits to see pending visual changes.
initial
2
Review Commit Detail
Click a commit to view changed visuals and approve or reject.
click
Bulk Actions
For large batches:
- Approve All: Accept all pending changes at once
- Filter & Approve: Approve by scenario or variant
Review Permissions
| Role | Can Review |
|---|---|
| Owner | ✓ |
| Member | ✓ |
| Viewer | ✗ |
Integrate with GitHub to get notified of visual changes via PR comments. See GitHub Integration.