Make WordPress Core

Changeset 61202


Ignore:
Timestamp:
11/11/2025 02:43:55 AM (5 weeks ago)
Author:
desrosj
Message:

General: Clarify that contributors should fork wordpress-develop.

Because WordPress/wordpress-develop is a mirror, the only way to contribute to WordPress on GitHub is by forking the repository (even when a contributor has write access as a Core Committer). This updates the “Getting Started” section to make this more clear.

The section about how to contribute using GitHub Codespaces is also being removed since this has been broken for some time (see #57896). This section can be reintroduced once the underlying tooling is fixed.

Props pbearne, desrosj, westonruter, wildworks, peterwilsoncc.
Fixes #64100. See #57896.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README.md

    r60504 r61202  
    77
    88## Getting Started
    9 
    10 ### Using GitHub Codespaces
    11 
    12 To get started, create a codespace for this repository by clicking this 👇
    13 
    14 [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://github.com/codespaces/new?hide_repo_select=true&ref=trunk&repo=75645659)
    15 
    16 A codespace will open in a web-based version of Visual Studio Code. The [dev container](.devcontainer/devcontainer.json) is fully configured with software needed for this project.
    17 
    18 **Note**: Dev containers is an open spec which is supported by [GitHub Codespaces](https://github.com/codespaces) and [other tools](https://containers.dev/supporting).
    19 
    20 In some browsers the keyboard shortcut for opening the command palette (Ctrl/Command + Shift + P) may collide with a browser shortcut. The command palette can be opened via the `F1` key or via the cog icon in the bottom left of the editor.
    21 
    22 When opening your codespace, be sure to wait for the `postCreateCommand` to finish running to ensure your WordPress install is successfully set up. This can take a few minutes.
    239
    2410### Local development
     
    4834#### To start the development environment for the first time
    4935
    50 Clone the current repository using `git clone https://github.com/WordPress/wordpress-develop.git`. Then in your terminal move to the repository folder `cd wordpress-develop` and run the following commands:
     36You can get started using the local development environment with these steps:
     37
     381. Go to https://github.com/WordPress/wordpress-develop and fork the repository to your own GitHub account.
     391. Then clone the forked repository to your computer using `git clone https://github.com/<your-username>/wordpress-develop.git`.
     401. Navigate into the directory for the cloned repository using `cd wordpress-develop`.
     411. Add the origin repo as an `upstream` remote via `git remote add upstream https://github.com/WordPress/wordpress-develop.git`.
     421. Then you can keep your branches up to date via `git pull --ff upstream/trunk`, for example.
     43
     44Alternatively, if you have the [GitHub CLI](https://cli.github.com/) installed, you can simply run `gh repo fork WordPress/wordpress-develop --clone --remote` ([docs](https://cli.github.com/manual/gh_repo_fork)). This command will:
     451. Fork the repository to your account (use the `--org` flag to clone into an organization).
     461. Clone the repository to your machine.
     471. Add `WordPress/wordpress-develop` as `upstream` and set it to the default `remote` repository
     48
     49After this, remember to run `cd wordpress-develop`.
     50
     51After either of the two options above, move to the repository folder `cd wordpress-develop` and run the following commands in a terminal:
    5152
    5253```
Note: See TracChangeset for help on using the changeset viewer.