v0 Keeps Creating a New Git Branch Each Time I Deploy AND New Vercel/v0 Project Each Time I Fork

First question, have you tried starting a new chat / project (as in start from home menu or choose “new chat”) and just import your github since you have a function version on there?

Second question:
Is the project you are having issues with, with the new or old v0?
Im assuming new since you no longer see the github branch menu.
That is “gone” in the new v0. I say “gone”, because its not “really” gone, its just new and different. When you duplicate branches to start a new one all of your branched chats (which branch in github) will show in your project (see image). Those “recent chats” are just my duplicated chat / branches which coincide with github, although they have been merged of course).


You can also check your github connection status, commits, etc in Settings now (see image)

1 Like

Hi, thank you so much for getting back to me. I’ve tried creating a new project by importing from Git, but it still pulls the broken version, which is why I’m at a loss.

I’m not a Git expert, but here is my confusion: since my code is correctly deployed on Vercel and Git shows no pending changes/nothing to compare, I should be seeing the functional version. Instead, v0 seems to be serving an outdated snapshot.

Regarding the old chats, they seem to have ‘archived’ themselves—they are now merged with the main branch and no longer allow me to branch off or revert to a specific state. It’s like the history is being locked in a ‘forward-only’ state.

Am I missing a setting, or is the new v0 environment failing to sync with the actual repository state? How do I switch to the correct branch on v0? Could you walk me through the steps to ‘un-merge’ or effectively re-branch from those previous states? Or, if they are permanently merged, is there a way to force a new branch from a specific commit in my GitHub history so I can bypass this ‘forward-only’ lock? Honestly, I do not want to have to create a new project everytime I need to go back a version.

Below:

I have successfully promoted this version on Vercel, and it is live on my production site. I assumed that this promotion would also reflect in my Git main branch—am I mistaken about that workflow?

Furthermore, if this version is verified on my live site, why would v0 not reflect this state? If v0 is supposed to be linked to my Git main branch, why is it serving an outdated version?


The old branch that I want that is active on Vercel:
image

image
Old chats do not allow me to back-track or use the work from that branch; instead, they just pull the current work of the lastest version that is non-functional:

Since this chat / thread has been goign on since December, I think it would be good for you to share your chat link so the team can possibly look at it. It seems there are some issues going on.

To help debug your v0 project, could you share your v0 chat link?
It looks like https://v0.app/chat/... — you can copy it from your browser’s address bar while in the chat.

You’ll also need to unlist the chat so our team can view it — here’s how: Sharing | v0 Docs

This helps the team reproduce what you’re seeing much faster. Thanks!