-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Clarify which repository to be forked (#26824)
- Loading branch information
1 parent
c573e0d
commit 1fa6b06
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,7 +23,7 @@ The key players in this story will be the `upstream` (the original GitHub reposi | |
#### Initial setup | ||
|
||
1. Read [the contributing guide](https://github.com/TheOdinProject/.github/blob/main/CONTRIBUTING.md) for the project. | ||
2. Fork the original ("upstream") repository into your own GitHub account by using the "fork" button at the top of that repo's page on GitHub. | ||
2. Navigate to the curriculum repository and fork the original ("upstream") repository into your own GitHub account by using the "fork" button at the top of that repo's page on GitHub. | ||
3. Clone your forked repository onto your local machine using something like `git clone [email protected]:your_user_name_here/curriculum.git` (you can get the url from the little widget on the sidebar on the right of that repo's page on GitHub). | ||
4. Because you cloned the repository, you've already got a remote that points to `origin`, which is your fork on GitHub. You will use this to push changes back up to GitHub. You'll also want to be able to pull directly from the original repository on GitHub, which we'll call `upstream`, by setting it up as another remote. Do this by using `git remote add upstream [email protected]:TheOdinProject/curriculum.git` inside the project folder `curriculum`. | ||
|
||
|