Merge branch 'main' into 404-redir

Author: Iam-Karan-Suresh

src/components/CollapsibleCode.js

@@ -0,0 +1,60 @@
+import React, {useState} from "react";
+import CodeBlock from "@theme/CodeBlock";
+
+export default function CollapsibleCode({
+  code,
+  language = "json",
+  previewLines = 10,
+}) {
+  const [expanded, setExpanded] = useState(false);
+  const codeLines = code.trim().split("\n");
+  const visibleCode = expanded
+    ? code.trim()
+    : codeLines.slice(0, previewLines).join("\n") + "\n# ...";
+
+  const handleCopy = () => {
+    try {
+      navigator.clipboard.writeText(code.trim());
+      const btn = document.getElementById("copy-full-code");
+      if (btn) {
+        const originalText = btn.innerText;
+        btn.innerText = "Copied!";
+        setTimeout(() => (btn.innerText = originalText), 2000);
+      }
+    } catch (err) {
+      console.error("Failed to copy code:", err);
+    }
+  };
+
+  return (
+    <div className="margin-vert--md">
+      {/* Pass the full code to CodeBlock so default copy button works */}
+      <CodeBlock language={language}>{visibleCode}</CodeBlock>
+
+      <div
+        style={{
+          display: "flex",
+          gap: "10px",
+          justifyContent: "flex-end",
+          marginTop: "-8px", // Pulls buttons closer to code block
+        }}
+      >
+        {codeLines.length > previewLines && (
+          <button
+            onClick={() => setExpanded(!expanded)}
+            className="button button--sm button--secondary"
+          >
+            {expanded ? "Show Less" : "Show More"}
+          </button>
+        )}
+        <button
+          id="copy-full-code"
+          onClick={handleCopy}
+          className="button button--sm button--primary"
+        >
+          Copy
+        </button>
+      </div>
+    </div>
+  );
+}

versioned_docs/version-3.0.0/ci-cd/github.md

@@ -34,10 +34,6 @@ GitHub scripts are the easiest way to integrate Keploy with GitHub. We will be u
   ...
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 ### Example with Scripts
 
 While using [express-mongoose](https://github.com/keploy/samples-typescript/tree/main/express-mongoose) sample-application with keploy test in GitHub CI, the workflow would like:-

versioned_docs/version-3.0.0/ci-cd/gitlab.md

@@ -41,10 +41,6 @@ keploy-test-job: # This job runs in the test stage.
     ...
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 Now that we have Keploy installed, and all ready, we need switch to path where `keploy` folder is present in our application and install all the application related dependencies. Since we are using [flask-mongo](https://github.com/keploy/samples-python) sample-application, steps in our `script:` would look like below:-
 
 ```yaml
@@ -66,17 +62,15 @@ In your `.gitlab-ci.yml file`, in last step we have `keploy test` command to run
 
 ### 📝 Note
 
-Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`...and thought, _"Wait, am I hacking the kernel or something?"_ 😅
+Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`
 
 Don’t worry — these are just there because **Keploy uses eBPF** (a cool Linux feature) to trace your app’s behavior.
 
 So we install `kmod`, `linux-headers-generic`, and `bpfcc-tools` to make that tracing possible.
 
-Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs` — it’s like giving Keploy the **backstage pass** it needs to watch your app in action.
-
-No black magic. Just some low-level Linux stuff helping your tests run like magic! 🪄✨
+Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs`
 
-We will get to see output : -
+We would output something like below:-
 
 ```sh
 $ keploy test -c "python3 app.py"  --delay 50

versioned_docs/version-3.0.0/ci-cd/jenkins.md

@@ -47,10 +47,6 @@ pipeline {
 
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 ### Example
 
 Now that we have Keploy installed, and all ready, we need switch to path where `keploy` folder is present in our application and install all the application related dependencies. Since we are using [gin-mongo](https://github.com/keploy/samples-go/tree/main/gin-mongo) sample-application, steps in our `script` would look like below:-
@@ -106,15 +102,13 @@ pipeline {
 
 ### 📝 Note
 
-Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`...and thought, _"Wait, am I hacking the kernel or something?"_ 😅
+Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`
 
 Don’t worry — these are just there because **Keploy uses eBPF** (a cool Linux feature) to trace your app’s behavior.
 
 So we install `kmod`, `linux-headers-generic`, and `bpfcc-tools` to make that tracing possible.
 
-Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs` — it’s like giving Keploy the **backstage pass** it needs to watch your app in action.
-
-No black magic. Just some low-level Linux stuff helping your tests run like magic! 🪄✨
+Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs`
 
 We would output something like below:-
 

versioned_docs/version-3.0.0/keploy-cloud/deduplication.md

@@ -1,7 +1,7 @@
 ---
 id: deduplication
-title: Remove Duplicates Tests 🧹
-sidebar_label: Remove Duplicate Tests 🧹
+title: Remove Duplicates Tests
+sidebar_label: Remove Duplicate Tests
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/installation.md

@@ -1,7 +1,7 @@
 ---
 id: cloud-installation
 title: Keploy Cloud Installation
-sidebar_label: Installation 🛠️
+sidebar_label: Installation
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/keploy-console.md

@@ -1,7 +1,7 @@
 ---
 id: keploy-console
-title: Keploy Console 📘
-sidebar_label: Keploy Console 🛠️
+title: Keploy Console
+sidebar_label: Keploy Console
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/mock-registry.md

@@ -1,7 +1,7 @@
 ---
 id: mock-registry
 title: Mock Registry
-sidebar_label: Mock Registry 📦
+sidebar_label: Mock Registry
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/new-application.md

@@ -3,7 +3,7 @@ id: application-settings
 title: Keploy Cloud Application Settings Guide
 description: Learn how to configure application settings in Keploy Cloud. Manage environments, toggle features, and optimize your testing setup with this step-by-step guide.
 
-sidebar_label: Add Application 📝
+sidebar_label: Add Application
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/testgeneration.md

@@ -1,7 +1,7 @@
 ---
 id: auto-test-generation
-title: Auto Test Generation 🚀
-sidebar_label: Test Generation 🚀
+title: Auto Test Generation
+sidebar_label: Test Generation
 tags:
   - Auto Test Generation
   - OpenAPI