Git previews, protections and troubleshooting
Use pull-request previews without exposing production resources and recover safely from authorization, build or merge failures.
Last updated 2026-08-17
What you'll achieve
- Know what an untrusted fork can access
- Protect production branches and require approvals
- Recover from common Git synchronization and build failures
Preview trust
A branch or pull request from the connected repository can use only explicitly enabled preview-scoped resources. A pull request from a fork is untrusted: it receives no BlinkHost secrets, database branch, production environment or tenant resource capability. Closing or expiry disables the preview.
Production protection can restrict the repository and branch pattern, require a committed-secret scan, require verified backend modules and require distinct approvers. Every approval is bound to the exact source commit; a new commit needs new evidence.
Diagnose the boundary
| Message | Meaning | Action |
|---|---|---|
| Authorization required | The GitHub App was removed, suspended or lost repository permission | Re-authorize the selected repository; do not reconnect an unrelated installation |
| Branch changed | Compare-and-swap prevented an overwrite | Pull, review the three-way result, resolve conflicts and push again |
| Manifest missing or invalid | An unattended build has no trusted instructions | Add a valid blinkhost.yaml and push it |
| Possible committed secret | Protection found credential-like source | Revoke the credential, remove it from current source and history as appropriate, then store the value in BlinkHost Secrets |
| Waiting for approvals | The exact deployment request has insufficient valid approvers | Ask an authorised, distinct approver to review that commit |
| Isolated build failed | Dependency install or frontend build exited in the managed builder | Open the bounded build log and fix the first actionable source error |
Provider outages are retried through the durable webhook inbox. BlinkHost never retries an ambiguous push as a new commit. Preserve the operation ID, repository, commit SHA, UTC time and visible error when contacting support; never send tokens, cookies or secret values.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.