Git Operation "Store to Repository" should not consider formerly deployed objects if already removed from Inventory

Current Situation

Currently when GIT operation "Store to Repository" is used, the setting "Deployed/Released" is active by default. If the user does not select any items the current folder is part of the subsequent request to search for already  deployed or released items of the given folder. Unfortunately items that have been previously deployed and later on removed will nevertheless be taken into account and "reappear" in the local repository after the store operation.

Desired Behavior

When the Git operation "Store to Repository" is used and "deployed/released" is activated, items that have been removed from a controller by the "remove" or the "revoke" operation should not be taken into account when storing items from the given JOC folder to the local repository.

Workaround

To get rid of unwanted items in the local repository when an unwanted item "reappears" after a "Store to Repository" operation, use the "Delete from Repository" operation to remove any unwanted item from the file system before using the "Push" operation.