Hello Vercel Community,

We’re investigating an automatic deployment issue on a Hobby project connected to a private GitHub repository.

Observed behavior

• Pushing to a feature branch and opening a pull request did not create a Preview.
• An additional empty commit did not trigger a visible deployment.
• No Vercel status check or rejection comment appeared on the pull request.
• GitHub Actions completed successfully.
• Manual CLI deployments to Preview and Production succeeded.

Checks already performed

• The Vercel GitHub App is installed, not suspended, and has access to the repository.
• The project is linked to the correct repository.
• Git deployment creation is enabled.
• Preview Branch Tracking covers all unassigned branches.
• The production branch is configured correctly.
• Ignored Build Step is set to Automatic, with no custom ignore command.
• No root-level vercel.json or now.json disables deployments.
• The commit author is recognized by GitHub as the repository owner.
• The 30 most recent deployment records all report CLI as their source.

The project’s Git link metadata also reports sourceless: true. We have not established whether that field is relevant.

Questions

1. Is there a read-only way to determine whether GitHub events were received, ignored, or rejected by Vercel?
2. Can the project appear connected while its event subscription or Git authorization is stale?
3. Does sourceless: true have any bearing on automatic Git deployments?
4. What diagnostic step should we take before considering disconnecting and reconnecting the integration?

Production is currently healthy following a manual deployment. We want to investigate without changing production settings or triggering additional deployments.

Thank you.