
Setup
1
Connect GitHub
Install the GitHub App and select your repositories.
2
Connect Vercel
If you’re on Vercel Pro/Enterprise, Deployment Protection blocks external access to previews by default.
- Connect Vercel
- Select projects to grant access
- Click Get Bypass Secret for each project
What's a bypass secret?
What's a bypass secret?
A token that lets automation access protected previews. Generate one in Vercel: Project → Settings → Deployment Protection → Protection Bypass for Automation.
Options
| Option | Description |
|---|---|
| Site auth | Test credentials for previews behind login. Use x_user/x_pass in prompts. |
| Path filters | Only test PRs touching specific paths |
| Check runs | Block merges until tests pass |
FAQ
How do I test authenticated pages?
How do I test authenticated pages?
Two options:Credentials — Add username/password in integrations page. Reference as
x_user and x_pass in prompts.Cookies — For complex auth (SSO, MFA), export session cookies from DevTools and paste as JSON in the integrations page.Why am I getting 403 errors?
Why am I getting 403 errors?
Vercel Deployment Protection is blocking access. Connect Vercel and add the bypass secret for your project.
Can I use this without Vercel?
Can I use this without Vercel?
GitHub Action
For non-Vercel deployments:MORPH_API_KEY in repo secrets.