As the operator of an Atlantis deployment, I want the option to prevent users from planning/applying PRs older than --checkout-depth to avoid Atlantis performing full clones.
Describe the solution you'd like
Add an additional --disallow-full-clone option to Atlantis server.
If enabled and the merge base isn't present in a shallow checkout^1, Atlantis will fail instead of performing a full clone.
Describe the drawbacks of your solution
This adds additional complexity to Atlantis.
Describe alternatives you've considered
It is hypothetically possible to implement this as a pre-workflow hook^2, however, such an implementation would be brittle, as it must independently communicate with SCM. A native feature seems relatively lightweight, and would be highly useful for operators using Atlantis in a monorepo.
Describe the user story
--checkout-depthto avoid Atlantis performing full clones.Describe the solution you'd like
--disallow-full-cloneoption to Atlantis server.Describe the drawbacks of your solution
Describe alternatives you've considered