Best practices for creating a new v0 chat using a different GitHub branch

v0
,
1

Hi there,

Please help to share steps-by-step Best Practice to Create A New Chat within the same project to use a different GitHub Branch.

Thanks.

4

Hey, Ferry!

Happy to help!

What you need to do is “Duplicate Branch…”

CleanShot 2026-01-23 at 16.19.03@2x
CleanShot 2026-01-23 at 16.19.03@2x1002Ă—616 42.9 KB

Then you can rename the branch…

CleanShot 2026-01-23 at 16.21.29@2x
CleanShot 2026-01-23 at 16.21.29@2x1054Ă—802 70 KB

And branch off :smiley:

Creating a new branch creates a new chat fork, the new chat will have the code but not the previous chat context. Essentially, “each branch = separate chat” with its own history.

Does that help?

5

Hi Pauline,

Thank you for sharing the steps. That help to answer part of the question especially if I already have the chat opened and connected to the main branch and I can keep duplicating it from the main branch.

The issue now, I don’t know how to create a chat with the main branch. If I start a new chat from inside a project in V0, it looks something like this:

1. Ask anything in the chat:

image
image1279Ă—564 8.66 KB

2. Then without a preview, there is no setting to connect or import or fork from the GitHub main branch.

image
image1681Ă—806 67.6 KB

3. But if I ask the chat to create a simple landing page just to show the preview so I can see the GitHub menu, there is no option to switch branch to main or other branches.

image
image1919Ă—854 111 KB

There must be a way to do it, I just don’t know it yet. Please help to advise what is the best to do that? Once the chat is connected to the main branch, all I have to do is to duplicate the branch from the main branch to create a new chat, is that correct?

While we are at this topic, can you please confirm if the steps below are correct if I’m using the GitHub branch as staging environment before applying to the main LIVE production or please let me know if there are better ways to do this as recommended by V0 or Vercel.

  1. Connect Chat to Main branch.
  2. Duplicate the chat from Main to create a new branch for example branch 1.
  3. Make changes in the new chat with branch 1.
  4. Once done, create pull request to merge the branch 1 with the main branch.
  5. Once the pull request or the merge has been completed, delete branch 1.
  6. Duplicate the chat again from Main to create a new branch for example branch 2.
  7. Repeat the steps 3 -6 for any new changes.

Thanks for your help.

Ferry

1 Like
6

I have this same exact issue, i have my main branch but cannot connect my v0 to my main branch after publishing changes to my main via my IDE. I want v0 to view my new changes but I am unable to figure out how to change my chat to my main branch, I am stuck on main-2!

7

@pawlean , just wondering if you have any updates on the previous question?

Thanks.

Ferry

1 Like
8

From your Projects list, can you see your project then click “New Branch” to start a new branch from main?

https://v0.app/@your-username/chat/projects

As you can see:

CleanShot 2026-01-27 at 21.03.43@2x
CleanShot 2026-01-27 at 21.03.43@2x1608Ă—804 146 KB

How to switch and manage branches in v0
9

Hi @pawlean,

Thanks. Yes, I can see and use it. It will create a new branch from the main branch nicely.

However, making changes, editing, and ask AI to make changes to the codes; I can’t see the option to publish or push changes to the GitHub branch. The publish button doesn’t detect the changes.

image
image991Ă—726 35.2 KB

I even try to make a slight change in the codes manually. It doesn’t detect the changes and I can’t publish or push the changes. Is this a bug?

Please help, I’m stuck with this for a few days now.

Thanks.

Ferry

10

Ah, I see! This does look like a bug. Can you share that chat link with me?

11

Hi Pauline,

This issue has been resolved now. Thanks for your help.

1 Like
13

Glad I could help!