user-guide: add troubleshooting entry for dvc-exp in shallow clones

content/docs/user-guide/troubleshooting.md

@@ -125,3 +125,53 @@ and retry the DVC command. Specifically, one of:
 
 [internal directories]:
   https://dvc.org/doc/user-guide/project-structure/internal-files
+
+## DVC Experiments may fail in Git shallow clones {#git-shallow}
+
+`dvc exp` commands use internal Git operations which may not work properly in
+[shallow clones](https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---depthltdepthgt).
+Local Git repositories can be unshallowed with `git fetch --unshallow`.
+
+Typically, however, this occurs in transient remote environments such as
+Continuous Integration jobs, which use shallow clones by default. In those
+cases, change their configuration to avoid shallow cloning. Common examples:
+
+<toggle>
+<tab title="CML">
+
+[CML](https://cml.dev/doc) has a convenient `--unshallow` option for it's
+[`ci`](https://cml.dev/doc/ref/ci) command:
+
+```cli
+$ cml ci --unshallow
+```
+
+</tab>
+<tab title="GitHub Actions">
+
+Set `fetch-depth` to `0` in the `actions/checkout` action:
+
+```yaml
+- uses: actions/checkout@v3
+  with:
+    fetch-depth: 0
+```
+
+> More info.
+> [here](https://github.com/actions/checkout#fetch-all-history-for-all-tags-and-branches).
+
+</tab>
+<tab title="GitLab CI/CD">
+
+Set the `GIT_DEPTH` env var to `0`:
+
+```yaml
+variables:
+  GIT_DEPTH: '0'
+```
+
+> More info.
+> [here](https://docs.gitlab.com/ee/ci/large_repositories/#shallow-cloning).
+
+</tab>
+</toggle>