Deleting an asset is unsuccessful if the asset is marked for add when using Git source control

Deleting an asset that is marked for add when using the Git source control plugin no longer actually deletes the asset. Instead the file will be removed from the Content Browser (it actually stays in the Content Browser after the delete process completes in 4.17), but the corresponding .uasset file remains in the project's Content folder on the disk, and when the project is opened again, those files will once again be seen in the Content Browser and will still be marked for add.

REGRESSION:
Yes. In 4.13, deleting an asset marked for add when using the Git source control plugin deleted the associated .uasset file from the project's Content folder as well, and the asset would not reappear in the Content Browser the next time the project is opened.

1. Create a new Blank Blueprint project.
2. Set the project to use Git source control.
3. Import any asset into the project.
   • This was tested using a skeletal mesh FBX file.
4. Once the import is completed, save all of the assets that were added to the project.
   • Once they are saved, all of the assets will be marked for add to the Git repo.
5. Select all of the new assets and delete them.
   • In 4.17, the delete process will complete but the assets will remain visible in the Content Browser. In 4.14 and 4.15, the assets will no longer be shown in the Content Browser.
6. Close the Editor.
7. Open a Windows Explorer window and navigate to the project's Content folder.
8. Note that the folder still contains .uasset files for the assets that were deleted in step 5.
9. Open the project in the Editor.

RESULT:
The previously deleted assets are once again present in the Content Browser, and are still marked to be added to the Git repo.

EXPECTED:
The deleted assets are no longer present in the Content Browser.