Deploy preview review
Turn each deploy preview into a reviewable screenshot
Capture the URL your hosting job produced, download a full-page PNG, and keep it beside the build. Reviewers get a concrete page state without opening every preview tab.
export SCRNIFY_API_KEY=...
export PREVIEW_URL=https://preview.example.com
capture_url="$(scrnify capture "$PREVIEW_URL" \
--type image --format png --full-page)"
curl -fsSL "$capture_url" -o deploy-preview.pngArtifact to keep
deploy-preview.png — a capture of the public URL at the time this command ran.
Run sheet
Capture only after the preview is reachable
- 01
Wait for deployment
Run capture after the host reports a ready URL. Pass that value through a job output, environment variable, or manual workflow input instead of hard-coding a temporary URL.
- 02
Capture one known viewport
Use --full-page for page-wide review, or set --width and --height for a stable viewport. Keep the same dimensions between runs when reviewers need a fair comparison.
- 03
Download the result
The CLI prints the captured asset URL on stdout. curl -f downloads it and makes an HTTP failure stop a fail-fast shell step.
- 04
Attach, then inspect
Upload the PNG with your CI provider’s artifact mechanism. A successful capture proves the file exists; a reviewer or visual assertion must decide whether the UI is correct.
Before sharing
Make the preview evidence useful
- Use a preview URL reachable from Scrnify’s hosted browser, not localhost or a private runner address.
- Capture after assets and the deploy itself are available; a successful deployment output is the clean handoff point.
- Keep API keys in CI secrets and pass SCRNIFY_API_KEY through the step environment.
- Name artifacts with a commit, branch, or pull-request identifier when several runs may be downloaded together.