Changes detected in target branch message returned when deploying
During this process, Copado might detect changes in the destination branch, which means that the deployment and merge in Git of the promotion branch into the destination branch might have been done incorrectly. These warnings may appear if several deployments have been made at the same time, or if the branches were modified manually while the deployments were being executed.
"Changes detected in target branch 'XXXXXXXXXXXX' during deployment execution. The promotion branch was not merged into the destination branch. Please try to restart the deployment or recreate the promotion branch out of the new target branch state. Promotion Branch = 'promotion/P05469-YYYYYYYYYYYYYYYY'"
The components in the deployment were deployed into the destination org, but the promotion branch was not merged into the destination branch. Re-deploying the deployment will ensure that the process is completed using the up to date status of the destination branch.
You can also create the deployment again from the Promotion record in order to create a new promotion branch from the updated destination branch.
"Changes detected in target branch 'XXXXXXXXXXXX' after promotion branch Promotion Branch = 'promotion/P05469-YYYYYYYYYYYYYYY' was created, please recreate promotion branch out of the new target branch state."
You need to create the deployment again from the Promotion record in order to create a new promotion branch from the updated destination branch. If this doesn't solve the issue, try adding @gitDepth=XXX to the name of the new Deployment record created from the promotion, where XXX is the depth of the history of the commits that are used.
"Changes detected in target branch 'XXXXXXXXXXXX' after creation of the Promotion Branch 'promotion/P05469-YYYYYYYYYYYYYYY', auto merge successfully performed to incorporate the last changes to the deployment."
No action is required in this scenario.