Heres what happened, we deployed the Metadata AND a ChatBot. As part of our deployment, we manually updated the metadatas to contain PROD relavent info (instead of ACC info that was pushed from ACC Branch)

I also discovered that there were duplicate utterances in the Chatbot which we had to remove via manual DML deletes to ensure that the Data Model was built properly.

Then, we wanted to deploy just a Field change, and did so by merging a PR containt just the Field Change into main in Azure. This, obviously, triggered a deployment and in that deployment, the metadata and the ChatBot were redeployed in their incorrect form as we had not back propagated the manual changes.

While we could/should have back propagated the Chatbot to remove the duplicates from the git branch version we dont want to move the metadatas back as we are only supposed to store keys and other sensitive PROD level info in the PROD environment only.

I removed all the 'API Key' Metadata records from the Default Metadata comparison on the CI job so we shouldnt run into this again for those types of data, but I still think that we need to be notified and/or given the opportunity to view the totality of the changes prior to deployment somehow as it is unexpected behavior to deploy 5 things as a result of 1 file change and have to undo/repair all the unexpected changes.