From caab25361251d69fd5bca81fee382b642bf2351a Mon Sep 17 00:00:00 2001 From: IvanYuriev2 <104007307+IvanYuriev2@users.noreply.github.com> Date: Wed, 14 Aug 2024 15:47:24 +0200 Subject: [PATCH] Update forks.md typos fixed and few more words added to describe "upstream" --- docs/repos/git/forks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/repos/git/forks.md b/docs/repos/git/forks.md index 5693a14b086..19f1f49c9c1 100644 --- a/docs/repos/git/forks.md +++ b/docs/repos/git/forks.md @@ -123,7 +123,7 @@ git remote set-url upstream ## Push local changes to your fork -When you fork, you create a personal version of the original repository ("upstream"). This version is independent of the original, though it shares the code and retains a link to the original repository, allowing for future synchronization. So, there's nothing to prevent you from working directly in the `main` branch of the local clone and then pushing that work to the `main` branch of your fork. However, it's generally better to use [feature branches](git-branching-guidance.md#use-feature-branches-for-your-work) for your work. By using feature branches: +When you fork, you create a personal version of the original repository (original repository is referred as "upstream"). Fork is independent from the upstream, but fork shares the code and retains a link to the upstream, allowing for future synchronization. So, there's nothing to prevent you from working directly in the `main` branch of the local clone and then pushing that work to the `main` branch of your fork. However, it's generally better to use [feature branches](git-branching-guidance.md#use-feature-branches-for-your-work) for your work. By using feature branches: - You can maintain multiple, independent workstreams simultaneously.