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 =)