---

Currently, pull-request pipelines always perform a full git clone and ignore the clone: depth setting in bitbucket-pipelines.yml.
This is because the PR build merges the destination branch into the source branch, which needs history back to the merge base.

Suggestion:

A built-in option for PR builds to avoid the full clone — either by honouring the configured clone depth, or by dynamically calculating the required depth from the merge base and fetching only the commits needed for the merge.