updated the git clone section to make it relevant (#7277)

Co-authored-by: Mohammad Humayun Khan <humayun@Mohammads-MacBook-Pro.local>
getsentry · Jun 27, 2023 · 3133a40 · 3133a40 · vercel · Jun 27, 2023
1 parent e35f9de
commit 3133a40
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/docs/product/sentry-basics/integrate-backend/fork_n_clone.png b/src/docs/product/sentry-basics/integrate-backend/fork_n_clone.png
diff --git a/src/docs/product/sentry-basics/integrate-backend/getting-started.mdx b/src/docs/product/sentry-basics/integrate-backend/getting-started.mdx
@@ -35,14 +35,14 @@ If you're using your own source code, you can skip this tutorial and either:
 
 2. Click on "Fork" and select the target GitHub account you wish this repository to be forked in to.
 
-3. Once the fork is complete, click on "Clone or download" and copy the repository HTTPS URL.
+3. Once the fork is complete, click on "Clone or download" and copy the repository URL. You can do this using HTTPS, SSH or via GitHub CLI.
 
    ![Clone Repository](fork_n_clone.png)
 
 4. Clone the forked repository to your local environment:
 
    ```bash
-   > git clone <repository HTTPS url>
+   > git clone <repository HTTPS or SSH url>
    ```
 
 5. Now that the sample code is available locally, open the `backend-monitoring` project in your preferred code editor.