Skip to content

Commit caab253

Browse files
authored
Update forks.md
typos fixed and few more words added to describe "upstream"
1 parent d3bdf75 commit caab253

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/repos/git/forks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ git remote set-url upstream <clone URL>
123123

124124
## Push local changes to your fork
125125

126-
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:
126+
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:
127127

128128
- You can maintain multiple, independent workstreams simultaneously.
129129

0 commit comments

Comments
 (0)