What action will Copado take if a feature branch does not exist and a metadata difference is found?

When a metadata difference is identified in Copado and the corresponding feature branch does not exist, the platform will create a new commit record. This action is crucial because it allows for proper tracking and documentation of changes made to the metadata. By adding a new commit record, Copado helps maintain a clear history of modifications, which is essential for collaboration and version control in a team environment.

Creating a new project would not be applicable in this scenario, as the focus is on addressing a metadata difference, not initiating a completely new project. Ignoring the changes would defeat the purpose of version control, as it could lead to discrepancies and a lack of visibility into important updates that need to be addressed. Lastly, proceeding with a branch deletion would only be relevant if a branch was being actively managed and needed to be removed, which is not the case if there is no existing branch to begin with. Therefore, adding a new commit record is the most fitting response when facing a metadata difference without an existing feature branch.