V0 do not merge incoming changes

I get v0 is an AI tool to accelerate our project and stuff but, saying v0 can pull updates from Github like in the newsletter

is kinda outrageous. I spent a whole day updating packages to their latest versions (which not even NextJS itself is in its latest version), fixed all code, improved several parts and much more and what v0 does? Yes, that’s right, reverted every single file to its previous known version. How do I know that?

Simple

This is the last commit of a branch created to push all updates
image

Then this is the related deployment
image

And this is what v0 looked like right after

image

Yes, it is a lot of files… a lot of things changed…

And there are WAY more than just these ones there

And then, what v0 do? Merged, learned the diff and move on? Leave it as it was? No! not v0! it just reverted the whole thing and **************** you basically!

So, basically, if you plan to create something by your own hand, create a new repo, use whatever v0 created, paste there and just move on with your life. Never try to do anything in this repo outside v0 and you are good

Really?

EDIT 1
oh, also, there is this reply here which I state some more stuff

When v0 syncs it will take the exact latest state of the repository. If you do not want that change, you can click “Restore” on your previous version before the sync and it will roll back, and you can unlink the branch so it doesn’t pull/push automatically

If you’re going to work on both v0 and locally at the same time on the same branch, make sure you pull the latest changes locally before committing

The most robust workflow though is to not link v0 to main, and instead do all of your work in a branch. Then when you’re happy with changes you can click the “Create pull request” button and merge it properly after reviewing changes

1 Like

When v0 syncs it will take the exact latest state of the repository. If you do not want that change, you can click “Restore” on your previous version before the sync and it will roll back, and you can unlink the branch so it doesn’t pull/push automatically

But this is EXACTLY what I want! I want to make some changes locally up to the point I want, then push it into the repo, expect that v0 will pull all these changes and just merge into it, not to take the exact latest state of the repository.. I want 0 to pull, merge, learn the diff and move on.

if only v0 could create a branch properly and use it, it would be amazing… but this isn’t the case, unfortunately. If I ask to v0 to create a branch, it won’t be created, no matter what. If I create a branch directly on Github, v0 do not sync and can’t see the branch created, no matter how many times I refresh the page. I waited for like, 2 hours, to see if the branch was created and… no, it wasn’t

This was my previous knowledge, I just checked and the branches are there and I could create a new branch inside v0 and also on Github.

And, I haven’t seen this ““most robust workflow”” anywhere. Is it written in some docs or something or is it like “auricular knowledge”?

and, comparing what you said to what I did, the only difference was unlinking v0 with main. Because a branch was created, a PR also, whole building process was done, exactly just like you said. v0 did read the changes, as you can see in the pictures the amount of green/red numbers in each file. I ran the whole project in my computer, everything was working perfectly fine.

Tomorrow I will do exactly like you said, I will try by the letter and see how things gonna go. But, before going whole in, I will do one little thing and see how v0 will behave, because if something small works, a big will also. Despite the fact v0 did read the changes but it doesn’t merge it. Is there, by any means, a way to force v0 to merge the diff and that is it?

It could have some options to deal with v0. A select, or radiobox group or something alike, asking some questions like


Are you an experienced developer?

[ ] Yes
[ ] No

How do you want my help?

[ ] 100% vibe coding
[ ] 70% vibe coding + 30% your code
[ ] 50% vibe coding + 50% your code
and so on

Would you like to pick the packages you want to install in advance, so I can init the project properly?

[ ] Yes
[ ] No

If the v0 user check yes, then

Please, provide the package name or github link

https://www.npmjs.com/package/shadcn

https://github.com/shadcn-ui/ui

So, in this way, it can get the latest version or allow the user to add the preferred version by using @

https://github.com/shadcn-ui/ui/releases

For example.


v0 could implement some way to fetch the latest version (like using Context7, I don’t know), or list the most used packages in all applications, like the top 300, update the LLM to these packages, with newest documentation and more what it can be used and so on.

By this way, I guess, it will take less time to the LLM to think in order to know exactly what will be used ( in case of the user being an experienced one) or not, v0 will use whatever it knows (if the user is 100% vibe coding)

Also, there are few other ideas to improve v0 in the Edit 1 here too , feel free to ask anything about them (or not, I don’t know)

And add a “force merge”, to pull and merge all incoming updates…

thanks =)

Another question regarding to this answer

how I will then merge my updates into v0? I mean… If I simply create the things I want in a branch (let’s say ‘updates’), merge ‘updates’ into the master branch, keep doing other things in v0 like adding new fields and stuff, if I can’t pull and merge into v0 branch (because you said take the exact latest state of the repository), whenever I push these v0 changes into master, it will have dozens and dozens of conflicts (which any dev wants that)…

So… what would I do in this case? How these v0 changes will be merged into master if I can’t pull & merge anything into it?

Just to know

Consider each v0 chat to be an independent branch. When you’re happy with one, you create a pull request and merge that into main, and then at any time you can create a new branch+chat from main to develop your next feature in v0

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.