cleanup-copy

To safely delete project copies after merging, validate the merge status and check for uncommitted changes in the copy before removal. This automated cleanup also removes associated Git remote references from the original project.

When cleaning up merged feature branch copies, the associated Git remote references in the original project are deleted. This reference management prevents clutter after the isolated development copy is safely removed.

You cannot safely remove an isolated project copy with uncommitted changes. The cleanup process checks for uncommitted changes in the copy before removal to ensure no local modifications are lost during deletion.

To clean up temporary development workflow copies, run the cleanup command followed by the specified feature name. This identifies the correct copy directory and remote name to validate and remove after merging.

Using an automated cleanup process for merged Git branches prevents clutter and potential data loss. It validates merge status and safely deletes the temporary copies, ensuring your code management workflow remains organized.