You might be overusing this technique. Configuration is a pretty abstract term, so don't get too hung up on "configuration must be text in version control."
Configuration settings checked into version control work well when the developer knows what these settings are ahead of time, the settings aren't sensitive in nature (e.g. a password or authentication token), and the end user doesn't need to change it. It's perfectly fine for a system to have configuration in files, the database, and even environment variables.
Trying to propagate database configuration settings into text files through automated triggers and pull requests just turns your CI/CD pipeline into a disjointed Rube Goldberg machine, and CI/CD pipelines are already a Rube Goldberg machine to begin with. Don't make it any worse on yourself.
You don't need a single source for configuration when the end user can change some of these settings themselves. Cobbling together a single source will only obfuscate this fact, making it harder to troubleshoot environmental issues later. Imagine an environmental problem arises, and the user is accustomed to pushing buttons to change a setting. Now they need to wait for a CI/CD pipeline and a pull request? Having admin screens should give users the power to change these settings easily and quickly. Smashing this into a CI/CD pipeline would be a frustrating experience.