Could you expand on this a little? I'm using Retool now for a client, and while some parts are a little shaky, I can see how it's saved a lot of time over developing internal dashboards from scratch.
You'll also inevitably need to go beyond the functionality that retool offers, at which point their development experience really breaks down, and you'll have to either come up with some bespoke workflow to integrate complex custom components, or migrate away.
Despite all this I really like it as a tool, it just needs to be approached with care.
The tool spreads "code" around in a lot of different ways, like mustache templates, transformers, and orchestrations. So it would be hard to keep track of all that without the git integration. I didn't look at it deep enough to see what dealing with, for example, a change in the source data schema would look like.