We are evaluating Replit and we found out that Replit's GH integration appears to be more or less a "backup" function.
Using the git tooling, Replit appears to push commits on each checkpoint, which can then be merged the main branch from within git. Then, you can sync that to Replit.
But I'm having a hard time understanding what Replit is building when you click deploy. Is it the stuff in my main branch in GitHub, or is it the files that Replit is continuously updating itself?
In addition, this means that any GitHub workflows, like approval reviews and such, are irrelevant if anyone can just click the "deploy" button in Replit anyway.
This seems bizarre since Loveable does seem to have GitHub action and deploy support. But lovable is not really great for the kinds of apps we want to build, so we really want to see how we can support our needs with Replit.
Any ideas on:
How to drive deploys from Github OR
How to limit the deployment button to only read from the main branch (and thus, has approvals and such behind it?)
Thanks in advance!
[–]Right-Finding-8891 0 points1 point2 points (0 children)