That said unless all these places (it appears to not just be 1) have the same backend and the tests are run against each location I'm not sure if CI/CD is the right answer.
It gave me a laugh for sure and reminded me the terror around kicking off a job in our production clone (the only way to fully test some queries/processes due to size and real-world data needed). We had scripts that wiped things like phone numbers, emails, SSN, etc before it hit the clone but not all developers where diligent about adding to the cleaning script when adding new fields to the DB. My nightmare was sending out a batch of SMS/Emails to people alerting them to an issue (the staleness of the data would fire off false alarms) that didn't exist.