Skip to content

Update 01-git-fork-vs-git clone.md #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Gowthams1999-commits wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update 01-git-fork-vs-git clone.md #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 02-git/01-git-fork-vs-git clone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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."

Expand Down