Consider this scenario: Using classic pipelines in Azure Pipelines, Bob builds the master branch (pointing at commit 201ef3b), creates a release for the build, and deploys it to production. Mallory then moves the master branch to their own commit without Bob's change (99187b4) and force-pushes.
Since no ref then points at 201ef3b (directly or indirectly), would Azure DevOps eventually purge/prune that commit, or would it retain it along with the build which has been deployed to production?
I've been unable to find this information in the documentation, so have submitted a github issue for it. As noted there, I did find information that deleted branches are retained indefinitely, but it's not clear if that's also true for orphaned commits, or if some cleanup occurs.
