Changeset 61202
- Timestamp:
- 11/11/2025 02:43:55 AM (5 weeks ago)
- File:
-
- 1 edited
-
trunk/README.md (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/README.md
r60504 r61202 7 7 8 8 ## Getting Started 9 10 ### Using GitHub Codespaces11 12 To get started, create a codespace for this repository by clicking this 👇13 14 [](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.23 9 24 10 ### Local development … … 48 34 #### To start the development environment for the first time 49 35 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: 36 You can get started using the local development environment with these steps: 37 38 1. Go to https://github.com/WordPress/wordpress-develop and fork the repository to your own GitHub account. 39 1. Then clone the forked repository to your computer using `git clone https://github.com/<your-username>/wordpress-develop.git`. 40 1. Navigate into the directory for the cloned repository using `cd wordpress-develop`. 41 1. Add the origin repo as an `upstream` remote via `git remote add upstream https://github.com/WordPress/wordpress-develop.git`. 42 1. Then you can keep your branches up to date via `git pull --ff upstream/trunk`, for example. 43 44 Alternatively, 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: 45 1. Fork the repository to your account (use the `--org` flag to clone into an organization). 46 1. Clone the repository to your machine. 47 1. Add `WordPress/wordpress-develop` as `upstream` and set it to the default `remote` repository 48 49 After this, remember to run `cd wordpress-develop`. 50 51 After either of the two options above, move to the repository folder `cd wordpress-develop` and run the following commands in a terminal: 51 52 52 53 ```
Note: See TracChangeset
for help on using the changeset viewer.