Issues with the new branch-based workflow in v0

Discussions
, , ,
1

This new requirement to create separate branches is unacceptable. It completely blocks my ability to test and evolve my work on the platform.

The previous pull/publish workflow was vastly superior and worked without issues. There was no need to replace it with something worse.

I use v0 daily, and in this month alone I’ve spent more than $450 on the platform. With this change, continuing to use v0 is no longer viable, and I will be forced to migrate to another solution.

This update is extremely bad and should be reconsidered immediately.

4 Likes
5

Correct.
If that is a new strategy: very bad. Combined with the changed pricing policy, even worse. Continous work seems to become impossible.

2 Likes
6

Yes, totally agree! I was forced to update and the new way of deployment is super annoying! I lost changes, have to merge new branches all the time and from an easy flow, we now moved to much more complex way of deployment.

Is there a way to switch back to the previous version of deployment?

1 Like