Find out why abandoned screenshots aren't being removed when running update_screenshots
The following discussion from !1179 (merged) should be addressed:
question (non-blocking): @pgascouvaillancourt do we have an issue open for auto removal of these kind of screenshots? Jest seems to do this nicely when screenshots are updated... Is this something storyshots can do?
When screenshots were pushed for some stories, renaming or deleting said stories should result in previously generated screenshots being removed when running the
update_screenshots CI job. This behavior is expected to work out-of-the-box since Storybook
v5.3.0-beta.9. However, we have noticed that multiple outdated screenshots have been hanging out in the repo and had to be removed manually.
Let's investigate to understand why those screenshots aren't being clean up automatically.