From 43685d9a9ab4e818bca05059792884addacf956a Mon Sep 17 00:00:00 2001 From: manikandan Date: Fri, 5 Sep 2025 22:34:18 +0530 Subject: [PATCH] test-change --- 02-git/01-git-fork-vs-git clone.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/02-git/01-git-fork-vs-git clone.md b/02-git/01-git-fork-vs-git clone.md index 7341abdf..8b69d8c7 100644 --- a/02-git/01-git-fork-vs-git clone.md +++ b/02-git/01-git-fork-vs-git clone.md @@ -8,7 +8,7 @@ This question is often asked to check if you understand collaboration workflows - **`git fork`** creates a **copy of a repository on your GitHub (or GitLab, etc.) account**, letting you propose changes without write access to the original repo. - **`git clone`** creates a **local copy of any Git repository** (your own or someone elseโ€™s) on your machine for development. -### ๐Ÿ“˜ Detailed Explanation +### ๐Ÿ“˜ Detailed Explanation. When you **fork** a repository on GitHub, you're telling the platform: > "I want a separate version of this repository in my own GitHub account."