wacky formatting

docs/docs/using-pants/using-pants-in-ci.mdx

@@ -133,12 +133,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.11/docs/using-pants/using-pants-in-ci.mdx

@@ -117,13 +117,16 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
     long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting
     at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before
-        and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before
+and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.12/docs/using-pants/using-pants-in-ci.mdx

@@ -117,13 +117,16 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
     long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting
     at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before
-        and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before
+and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.13/docs/using-pants/using-pants-in-ci.mdx

@@ -122,12 +122,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.14/docs/using-pants/using-pants-in-ci.mdx

@@ -126,12 +126,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.15/docs/using-pants/using-pants-in-ci.mdx

@@ -128,12 +128,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.16/docs/using-pants/using-pants-in-ci.mdx

@@ -128,12 +128,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.17/docs/using-pants/using-pants-in-ci.mdx

@@ -126,12 +126,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.18/docs/using-pants/using-pants-in-ci.mdx

@@ -126,12 +126,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::
 

versioned_docs/version-2.19/docs/using-pants/using-pants-in-ci.mdx

@@ -130,12 +130,15 @@ GitLab's merge pipelines make a shallow clone by default, which only contains re
 
 1.  Clone the entire repository by going to "CI / CD" settings and erase the number from the "Git shallow clone" field of the "General pipelines" section. Don't forget to "Save changes". This has the advantage of cloning everything, which also is the biggest long-term disadvantage.
 2.  A more targeted and hence light-weight intervention leaves the shallow clone setting at its default value and instead fetches the `main` branch as well:
-    `    git branch -a
+
+```
+git branch -a
 git remote set-branches origin main
 git fetch --depth 1 origin main
 git branch -a`
+```
 
-        The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
+The `git branch` commands are only included to print out all available branches before and after fetching `origin/main`.
 
 :::