Preview Deployments not triggering for private repository

Help
1

Current versus Expected behavior

Current Behavior: When I push a new, non-production branch (e.g., feature-story) to our private GitHub repository, no new deployment is triggered on Vercel. The “Deployments” tab only ever shows deployments from our production branch (main). Vercel seems to be completely unaware of any other branches.

Expected Behavior: When a new branch is pushed to our private GitHub repository, a new Preview Deployment should be automatically created on Vercel, and it should appear in the “Deployments” tab.

Steps to Reproduce and Troubleshoot

The issue seems to be with the Git integration itself, as it has persisted across projects and after extensive troubleshooting.

  1. Push a new branch (e.g., feature-story) from local machine to the private GitHub repository IT-OZISAN-KY/historical-map-app.
  2. Observe the “Deployments” tab on the corresponding Vercel project. No new deployment is initiated.
  3. Troubleshooting 1: Permissions: We have repeatedly re-installed and re-configured the Vercel App within GitHub to ensure it has full access to this private repository.
  4. Troubleshooting 2: Project Settings: We have verified the Root Directory is empty (correct) and the Ignored Build Step is “Automatic” (default).
  5. Troubleshooting 3: Project Recreation: We have completely deleted the Vercel project and created a new one by re-importing from the same GitHub repository. The issue persists even with a fresh project.
  6. Troubleshooting 4: Manual Redeploy: When attempting to “Redeploy” from the Vercel dashboard, the dialog only shows the main branch and does not provide an option to select or input another branch name, confirming Vercel is not aware of other branches.

Project Information

  • Framework: Next.js
  • Environment: Production deployments from the main branch work as expected. The issue is specific to Preview Deployments for other branches.
  • Project Settings:
    • Git Repository: https://github.com/IT-OZISAN-KY/historical-map-app (Private)
    • Root Directory: Not set (Project is at the repository root)
    • Framework Preset: Next.js
3

What happens if you deploy using the CLI?

4

Most of the time this issue is caused by the author of the git commit not being a member of the Vercel team. For private repositories in organizations, deploys can only be created via commits from members of the team. If this is the case, you should be getting an email on each failed deploy informing you of the issue

2 Likes
5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.