Reproduction

1. Have a Vercel project connected to a GitHub repository through the Vercel GitHub App.

2. Pick an existing commit SHA, for example 0b78a8ecf2f653cd47fe1709c81e4f3223f76d5b.

3. Push that exact commit to a branch that matches the project’s Git / ignored build rules, for example:

   1
   git push origin 0b78a8ecf2f653cd47fe1709c81e4f3223f76d5b:stg/test/deploy

4. Verify that Vercel creates a deployment.

5. Push the same commit SHA to another branch:

   1
   git push origin 0b78a8ecf2f653cd47fe1709c81e4f3223f76d5b:stg/test/deploy-2

6. Check Vercel deployments and activity logs with the dashboard or CLI/API.

Expected Behavior

Vercel should create a separate Git deployment for each branch push, even if the commit SHA is identical.

Actual Behavior

• Only the first branch push creates a deployment.
• GitHub branch push succeeded.
• Vercel GitHub App integration is connected.
• New commit pushes trigger Vercel deployments normally.
• No GitHub webhook is configured manually.
• Vercel activity/deployment search after the later push showed no new deployment.