When Git-controlled assets are deleted from Information Server then it is the developer's responsibility to ensure that the asset is also removed from the associated Git repository. Data Migrators consider the automation of asset deletion Deletion from a development environment a potentially dangerous practicealways comes with risk. MettleCI therefore takes the cautious approach of allowing developers to specify explicitly when assets are to be removed from the corresponding Git repository. This approach keeps developers in control , and also protects against accidental deletion.
Remember that your MettleCI-managed Git repository is a regular Git repository, so your existing Git user interfaces and git commands will work as normal.
If you wish to delete a DataStage asset from Git artefact using the MettleCI Workbench then simply...
Delete the artefact asset in the DataStage repository (using your DataStage client, for example), then
Commit the no-longer-existing asset using the 'Commit' option in the MettleCI Workbench.
When you do this the specified asset (or assets) is/are removed using a Git commit. This approach ensures that the Git history is not lostretained for that asset, and that the asset removal is associated with a Work Item Management story to maintain clear visibility of Developer behaviourto support traceability of all version control actions.