[wp-meta] [Making WordPress.org] #8007: Rewrite and clarify “Adding your GitHub fork to your WP trunk copy” section for accuracy and readability

[Making WordPress.org]

#8007: Rewrite and clarify “Adding your GitHub fork to your WP trunk copy” section
for accuracy and readability
-------------------------+-----------------------
 Reporter:  tomd6r       |       Owner:  psykro
     Type:  enhancement  |      Status:  assigned
 Priority:  low          |   Milestone:
Component:  Handbooks    |  Resolution:
 Keywords:               |
-------------------------+-----------------------

Comment (by psykro):

 @tomd6r I agree with your suggestion, during my first pass at the rewrite
 I actually considered leaving out the remote forks bit entirely.

 What about just adding this line to cover that use case?

 ==

 While first forking the mirror and then cloning it locally is recommended,
 if you've already cloned the `wordpress/wordpress-develop` mirror, you can
 add your fork as a remote repository using `git remote add`.

 `git remote add fork git at github.com:your-username/wordpress-develop.git`

 You'll then still be able to create a local branch, but will need to push
 to the correct remote.

 To learn more about working with remote repositories, see the [GitHub
 documentation](https://docs.github.com/en/get-started/git-basics/managing-
 remote-repositories).

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8007#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org