Why might a commit show "No changes" after attempting to delete a custom object?

When a commit shows "No changes" after attempting to delete a custom object, one of the primary reasons could be that the object was already deleted. If the custom object has already been removed in the base branch or any prior commits, then any subsequent commit that attempts to delete the same object again will reflect no changes. This situation arises because version control systems, like Git, only track modifications and will not display an action for deleting something that is already absent.

The scenario where the base branch is incorrectly set to master might lead to confusion in tracking changes; however, it does not directly result in a "No changes" message related to deletions. Issues with credentials or a corrupted Git repository would typically manifest as authentication failures or errors in accessing the repository, rather than the commit reflecting no changes.

Therefore, if the intent is to confirm an accurate state of the object after deletion, it is crucial to ensure that the object indeed existed prior to the deletion attempt. If it did not, no changes will be found in the commit.