I’m not a developer so don’t have formal training despite Replit providing super powers to build stuff. But I do run a different software business and have many very experienced developers. When we deploy we work on branches and merge them and run some pretty robust build tests to check conflicts and issues during code review.
When I start building a feature on my large Replit project, I kinda either have to finish it or throw it all away if it goes sideways. I always fear not being able to find the right “go to this checkpoint” that brings me back to before i started mucking something up if I’m taking on a big new effort. Or worst case I’m midway through something but have broken some other stuff in the process that I haven’t been able to clean up or test and I have an actual issue on the deployed app that needs a quick fix.
My issues/question is - what is the approach on doing some sort of branches or ways to start work on a feature that may take a while without basically blocking any sort of other intermediate needs for deploys while that work is in flight?
Does that make any sense what I’m asking?
It makes perfect sense. Commenting to follow…
I’ve found the Git tab more useful for rolling back then the rollback feature. Rollback seems limited by whatever the most recent chat was, but with the Git version control, you can roll back to anytime there was a commitment.
The unfortunate part about this is any db changes don’t reflect, and you end up with a mess.
Can you share your workflow or process how exactly you do this? I am beginner and would love to try this.
So far I have created repo on Github and synchronize it everytime I make successful changes but I am not sure how to use Git if I need to rollback to a previous working version.
@realfunnyeric good point, if you want to rollback to a previous version the database is not updated accordingly.
I’ve only had to do it a few times, but if you acccess the git tab, you can see the commits the Agent has done on your behalf and roll those back manually, vs using the rollback function in the chat.
Commenting for reach. I’d like to see a way to create/update/merge/deploy through branches.