Hi everyone,
I’m trying to understand and resolve a recurring issue with Vercel’s GitHub integration.
We have a project connected to GitHub. Vercel successfully builds and deploys our preview deployments, and the deployments reach Ready. However, the corresponding GitHub pull request check for our primary Vercel project remains stuck on:
“Vercel is deploying your app.”
The strange part is that we have a second Vercel project connected to the same GitHub repository and production branch. For the exact same commit, that second project completes deployment and correctly reports a successful status to GitHub.
We’ve observed this behaviour repeatedly across multiple pull requests, not just one.
For our latest example, PR #96:
- The primary project’s deployment reached Ready.
- The secondary project’s deployment also reached Ready.
- Both used the same commit and completed the same build process.
- The secondary project’s GitHub check reported success.
- The primary project’s GitHub check remained pending.
We’ve already checked the repository connection, production branch configuration, deployment logs, and relevant Git integration settings. We haven’t found a build failure or an obvious configuration difference that explains the behaviour.
What we’d like to understand:
- Can a Vercel deployment successfully reach Ready while its GitHub deployment-status callback fails to update the corresponding PR check?
- Could Hobby plan limits, GitHub API rate limits, or integration throttling cause this?
- Is there a way to inspect whether Vercel attempted to send the deployment status to GitHub and what response GitHub returned?
- Could this be a project-specific GitHub integration issue?
We’d appreciate suggestions from anyone who has experienced this or understands how Vercel reports deployment statuses to GitHub.
Our goal is to identify and fix the underlying cause. We don’t want to bypass the check or force it to appear successful when the actual status hasn’t been reported correctly.
Thanks.