[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Vercel deployments not auto-promoting to production from main branch

68 views · 1 like · 7 posts


George (@georgebobby) · 2026-02-26

## Problem
I was pushing changes to a repository, and it used to auto-promote the latest push to the `main` branch to production. Now it is not. I suspect I made changes to the settings but can’t find where to revert them.

## Current Behavior
- The commit `fix convex` is the latest production build on the `main` branch.
- I pushed new changes titled `google analytics` to the `main` branch.
- The new deployment stayed as a preview and I had to manually promote it to production.

## Question
Is there a way to properly revert this setting so that pushes to `main` automatically promote to production?

![image](https://global.discourse-cdn.com/vercel/original/3X/a/5/a5327d4c2dbc173fe315304e751ba2bc5db50244.jpeg)


Pauline P. Narvas (@pawlean) · 2026-02-26

Hey, George! Welcome to the Vercel Community :waving_hand: 

Since we want to make sure your `main` branch is actually triggering those live updates, could you try checking these settings?

First, head over to your project in the Vercel Dashboard and navigate to the **Settings** tab, then select **Git** from the sidebar.

Once you are there, look for the **Production Branch** section. You want to make sure your `main` branch is explicitly set as the production branch. Also, double-check that the option for **Automatically promote successful deployments** is enabled. This is usually what ensures your latest push actually goes live without manual intervention.


If those settings look correct but it still isn't working, there are a few other things that might be interfering. Sometimes the production branch setting gets accidentally pointed to a different branch during a test.

It is also possible that auto-promotion was disabled globally in your Git settings at some point. Another thing to look out for is a **deployment protection rule**. If you have specific environments protected, it might be preventing that automatic promotion to production until certain checks are met.


George (@georgebobby) · 2026-02-27

I found it here under Settings → Environments → Production → Automatically promote successful deployments. 


But still facing this issue below

![image|690x209](upload://62VpmEdXeBbO3qSyQOIsvOwZHh2.png)

![image|690x143](upload://sTENM3qwqJXmMa2UdKmOGex7aHP.png)

Earlier I used to get PR comments and checks like this, but not now. This is my vercel config for reference

![image|690x385](upload://7BPrtfAexM0MP2eEh9dt6aQCEGw.png)

I tried reconnecting it as well.


Pauline P. Narvas (@pawlean) · 2026-02-27

Have you tried with a new PR?


George (@georgebobby) · 2026-02-27

Thanks, I was able to fix the issue.


Pauline P. Narvas (@pawlean) · 2026-02-27

What did you do? Would be helpful for others in the community :slight_smile:


George (@georgebobby) · 2026-02-27 · ♥ 1

I had to enable it in all 3 environments (Production/ Preview/ Development). That was it.