We noticed that Digger backend can still get triggered using commentOps on old merged PRs.

If the merged PRs feature branches are deleted, the backend is not able to read digger.yml (that's fine)

However, when restoring the branch, we can trigger the backend with digger plan or digger apply and it will run successfully, the output will then show that resources will be destroyed which is expected since the old branch doesn't have the latest resources in the main branch. Moreover, digger apply can be run without any restrictions.

This is bad and a serious issue as it can result in the destruction of existing infrastructure