From d13f9776638ef837b1d0a2a966c25bce1b27cd8b Mon Sep 17 00:00:00 2001
From: Katrina Prosise <katrina.prosise@foundries.io>
Date: Mon, 2 Mar 2026 08:03:22 -0500
Subject: [PATCH] Add bitbucket example for secrets
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Added as tabbed content, which is largely the same.

QA: Edited with linter on, and checked built content in browser.

This commit applies to issue FFTK-3400, "…Bitbucket git secrets config…"

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
---
 .../lmp-customization/linux-extending.rst     | 48 +++++++++++++++----
 1 file changed, 39 insertions(+), 9 deletions(-)

diff --git a/source/user-guide/lmp-customization/linux-extending.rst b/source/user-guide/lmp-customization/linux-extending.rst
index 0be6e61f..2822f19e 100644
--- a/source/user-guide/lmp-customization/linux-extending.rst
+++ b/source/user-guide/lmp-customization/linux-extending.rst
@@ -180,7 +180,7 @@ For example, the OP-Tee package is only included in an image if the target machi
 
 .. _ref-ug-private-repo:
 
-Including Private Git+ssh Repositories
+Including Private Git+SSH Repositories
 --------------------------------------
 
 Custom recipes may need access to private Git repositories only available via SSH.
@@ -193,17 +193,47 @@ Secrets matching the pattern ``ssh-*.key`` are loaded into an ssh-agent, and ``s
 
 To generate ``ssh-known_hosts``:
 
-.. code-block:: console
+.. tab-set::
 
-   $ ssh-keyscan github.com > /tmp/ssh-known_hosts
+   .. tab-item:: GitHub
 
-An example for accessing a private GitHub repo:
+      .. code-block:: console
 
-.. code-block:: console
+         $ ssh-keyscan github.com > /tmp/ssh-known_hosts
+
+   .. tab-item:: Bitbucket
+
+      .. code-block:: console
+
+         $ ssh-keyscan bitbucket.org > /tmp/ssh-known_hosts
+
+Examples for accessing a private repo:
+
+.. tab-set::
+
+   .. tab-item:: GitHub
+
+      .. code-block:: console
+
+         $ fioctl secrets update ssh-github.key==/tmp/ssh-github.key
+         $ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts
+
+      At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like:
+
+      .. code-block::
+
+         SRC_URI = "git://git@github.com/<repo>;protocol=ssh;branch=main"
+
+   .. tab-item:: Bitbucket
+
+      .. code-block:: console
+
+         $ fioctl secrets update ssh-bitbucket.key==/tmp/ssh-bitbucket.key
+         $ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts
+
+      At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like:
 
-   $ fioctl secrets update ssh-github.key==/tmp/ssh-github.key
-   $ fioctl secrets update ssh-known_hosts==/tmp/ssh-known_hosts
+      .. code-block::
 
-At this point new CI jobs will be able to access recipes that have ``SRC_URI`` items like::
+         SRC_URI = "git://git@bitbucket.org/<repo>;protocol=ssh;branch=main"
 
-  SRC_URI = "git://git@github.com/<repo>;protocol=ssh;branch=main"