Which statement is NOT true about Destructive Changes?

The statement that is not true about Destructive Changes is that the component needs to be manually removed in the destination org after deploying the destructive changes. In the context of Copado, when destructive changes (such as deletions) are deployed, they are intended to remove components from the destination org automatically without the need for manual intervention. This aligns with how destructive changes are designed to work, as they effectively manage deletions through the deployment process itself, providing consistency and reducing the risk of human error post-deployment.

Typically, any component marked for deletion will be handled systematically within the deployment, ensuring that the appropriate components are removed from the target environment as intended. This automatic handling makes the deployment process smoother and helps maintain coherence between environments.

Regarding the other statements, they reflect accurate behaviors associated with destructive changes: deleted components are correctly flagged as Git Deletions, references to deleted components may indeed need to be deleted, and components must be removed in the source org as a prerequisite for creating a destructive change commit.