Problem statement

Gowtham was unable to do destructive changes in https://syensqo-icare.lightning.force.com/lightning/r/copado__User_Story__c/a7ZPH0000001Ym12AE/view, the commit appeared as Empty (destructive changes of Opportunity_Line_Item__c.GBU__c field)

Fix - TL;DR;

The problem is that the base branch was the default (master), and this Opportunity_Line_Item__c.GBU__c field was still not in master, therefore there was nothing to remove in the created branch (expected). To fix it:

  1. In Gitlab deleted the original branch created in https://syensqo-icare.lightning.force.com/lightning/r/copado__User_Story__c/a7ZPH0000001Ym12AE/view
  2. In Gitlab, recreated the original branch from feature/US-0003461
  3. Setup feature/US-0003461 as base branch in https://syensqo-icare.lightning.force.com/lightning/r/copado__User_Story__c/a7ZPH0000001Ym12AE/view, because US-0003461 is the last user story that modifies this field
  4. Perform destructive change again

Note that the first two steps are not required if no commit has been attempted (copado has not created any branch until a commit is attempted).

Troubleshooting process (includes all verifications done)

It was not required, due to the clarity of the situation

Is the problem/blocker due to Copado?

No

Is the problem due to a bad practice?

Partially - The base branch should have been set before trying to do any destructive change, knowing that the metadata to be deleted is not yet in production (master branch). The other part of the problem is understanding how copado git branching works behind the scenes to quickly understand the problem.

Is the problem due to an incorrect configuration of Copado?

No

Lessons learned

For destructive changes: