Hey guys
quick question…
I’ve been using v0 and usually cost cents to use and everything… but how this amount has been used, since basically what I did in this day was literally only revert the changes I did locally and v0 did not "quite get the changes and auto reverted it to its previous state, just like I stated here.
Am I missing something? Because what I did was basically pushing some local code to the github repo, v0 pulling the updates and, to discover in the, it restores to its previous state, as I learned here
So, does v0 charges me to pull up whatever I did locally and also to restore it to its previous state?
Thanks
v0 does not charge credits for the git sync features
After v0 synced the latest state, you prompted “Merge all incoming updates” with the v0 Large model, which caused it to pass all recently changed files back into the model, which was a lot of tokens and that’s what that $3.15 was
When you push a local commit it will sync in v0 with that exact code, so if you have any work in progress edits you’ve made those will be lost. I recommend working in separate branches or having a more strict handoff procedure between when you finish in v0, then pull the latest locally, make your changes, and commit and wait for it to sync before returning to v0
After v0 synced the latest state, you prompted “Merge all incoming updates”
Yes, I did that for one particular reason… In this reply here (posted at Jun 6, 12:07 PM), I had tried to merge updates I did in my local machine and v0 restored the last state (as you mentioned but I haven’t had this knowledge in that time). So, after some days, I got this email from v0
via email at Jun 9, 2025
With this tweet, so I really thought that would be that easy. Do my things, push and done. But, in the fear to lose what I have done, I asked to merge but, in the end, it seems any way works and I have lost $3.15
This is my concern. Old knowledge had been replaced by a new knowledge but both didn’t worked, I lost $3.15 and now I will spent much more time duplicating whatever v0 does, in fear to have codebase destruction (which it does completely randomly and we have to spend much more time and money to restore it) and keeping the code up to date with the latest packages versions, which even NextJS (where v0 should completely excels) is not updated to its latest version (which is a shame… lets face it)
Well… basically is this
