Update GitHub CLI fork command in README

[MakarandMane]

This PR updates the GitHub CLI example used when forking the wordpress-develop repository.

Current command

gh repo fork WordPress/wordpress-develop --clone --remote

Updated command

gh repo fork WordPress/wordpress-develop --clone

Why?

While following the contributor documentation for the first time, I encountered the following error when running the documented command with GitHub CLI 2.94.0:

the `--remote` flag is unsupported when a repository argument is provided

Running the command without --remote successfully:

• Forked the repository.
• Cloned it locally.
• Added the upstream remote as described in the documentation.

This update aligns the documentation with the current behavior of the GitHub CLI and helps prevent confusion for new contributors.

Fixes: https://core.trac.wordpress.org/ticket/65542

Use of AI Tools

AI assistance: Yes

Tool(s): ChatGPT

Model(s): GPT-5.5

Used for: Drafting the Trac ticket and pull request description. I verified the issue, tested the commands locally, and reviewed the final content before submission.

[github-actions]

Hi there! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

• PHP Coding Standards
• CSS Coding Standards
• HTML Coding Standards
• JavaScript Coding Standards
• Accessibility Coding Standards
• Inline Documentation Standards

Thank you,
The WordPress Project

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props mkrndmane.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.