[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 tomd6r):

 > I assume the git remote add command here is if you have cloned the
 original WordPress/wordpress-develop repository by mistake, instead of
 first forking it, and then cloning your fork?

 @psykro Good question! Yes — the `git remote add fork` command is helpful
 if you’ve cloned the upstream repo by mistake and need to push changes to
 your own fork. But it’s also useful more generally — for example, if
 you’re working from an existing clone (regardless of how it was set up)
 and want to add your fork as a remote to contribute via GitHub.

 We could clarify that by updating the wording to something like:

 ----

 If you cloned `wordpress/wordpress-develop`, or already have a local clone
 without your fork as a remote, you can add it like this to push your
 changes:

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

 Let me know what you think!

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