Fix · Vercel and deploying

Pushing to GitHub does not start a deployment

Not checked against the vendor's current screens

What you may see

I push but Vercel shows no new deployment
Deployments stopped appearing after I changed something

Most likely cause

The link between the GitHub repository and the Vercel project is broken, the branch is not the production branch, or the commit author is not allowed on the team.

Check first (about two minutes)

Open the project's Git settings in Vercel: is the right repository connected, and which is the production branch?
Check that the commit really reached GitHub (look at the repository page).

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who deploys websites on Vercel every day and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
Pushing to GitHub does not start a deployment

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
The link between the GitHub repository and the Vercel project is broken, the branch is not the production branch, or the commit author is not allowed on the team.

DO THESE STEPS, IN THIS ORDER
1. Confirm the push arrived on GitHub on the branch I expect (git log origin/<branch> -1).
2. Tell me what to check in the Vercel project: the connected repository, the production branch name, the "ignored build step" setting, and the commit author rules (names may differ).
3. If the link is broken, tell me how to reconnect the repository without deleting the project.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A new deployment appears within a minute of a push.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not delete and recreate the Vercel project as a first step.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Confirm the push arrived on GitHub on the branch I expect (git log origin/<branch> -1).
Tell me what to check in the Vercel project: the connected repository, the production branch name, the "ignored build step" setting, and the commit author rules (names may differ).
If the link is broken, tell me how to reconnect the repository without deleting the project.

Do not do this

Do not give Vercel access to all repositories if one is enough.
Do not delete and recreate the Vercel project as a first step.

Try another entry