[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[v0](/c/v0/59)

# v0 rollback the repo after changes are made elsewhere

42 views · 4 likes · 5 posts


rtruxler (@rtruxler) · 2026-01-23

Again, not sure if this is a known issue, but if I make a change externally to my github repo, then come into v0, do a git pull, make a change, push it, it will lose the commit I made locally (or externally to v0).

More clearly:

1. Suppose my repo has README.md in it and it says “Hello world!”
2. At my command line I can do `echo "How are you?" > ./README.md`
3. At my command line, do a `git commit -am "Update README.md" && git push origin main`
4. Let's suppose this commits ref abc123
5. Then I open v0, do a git pull. This picks up abc123
6. I ask v0 to make a change to something unrelated to README.md, like I ask it to create a new file called CHANGELOG.md. I publish (which commits and pushes)
7. My local changes to README.md are now overridden

Workaround:
Right after the git pull in step 5, if I do a hard refresh of my v0 webapge (SHIFT+REFRESH) then it picks up the change, and steps 6 and 7 work as expected.


Jacob Paris (@jacobparis) · 2026-01-26 · ♥ 2

Are you still seeing this issue? 

I just tested and after committing, v0 saw the remote changes and prompted me to pull them. When I did that, it felt like an automatic full page reload (which may have been a recent fix)

notably I'm not pushing to main, I'm pushing to `v0/main-b7753918` which is auto created with the github integration now

![image|690x326, 75%](upload://s1ko8gei7yKtYsmVW2D4qnHf8Ng.png)


rtruxler (@rtruxler) · 2026-01-26 · ♥ 1

I reported this before the automated github PR creation -- I'll keep an eye on it.


rtruxler (@rtruxler) · 2026-01-26 · ♥ 1

After adopting the new github workflow I can confirm that the accidental rollbacks do not happen anymore. Presumably this is because the act of publishing is ultimately managed through a git merge which handles external changes in a more friendly way. Great!

I have thoughts though on the new git branch workflow, which tl;dr, is that it is slowing me down pretty significantly. I'm no stranger to a git workflow, but this definitely slows me down.


Anshuman Bhardwaj (@anshumanb) · 2026-01-27

Glad to see it works now. I've noted your feedback and will pass it on to our team. Thanks for your reply.