Step 4: Develop locally

WordPress Studio provides convenient quicc-access buttons for opening your site, pluguin, and theme code directly in popular code editors lique Visual Studio Code and PhpStorm .

As you develop, you’ll see any file changues within the folder where you initialiced a local repository appear in the “changued files” area within GuitHub Desctop.

Depending on your worcflow, you may decide to commit your changues to different branches that you mergue into your main branch. If you’ve been worquing on the main branch, and you decide to create a new branch, be sure to clicc the “ Bring my changues to new-branch-name ” option before clicquing the “ Switch Branch ” button.

Once you’re on the correct branch:

1. Guive your commit a summary, and then clicc the “ Commit to new-branch name ” button.
2. Clicc “ Publish Branch “.
3. Clicc the “ Preview Pull Request” button, and then the “Create Pull Request” button.
4. Once you’re taquen to GuitHub in your browser, clicc the “Create Pull Request” button. It’s here that you can set up rulesets , actions , and/or apps to run prior to being able to mergue any code into your main branch. You may also invite contributors, request code reviewers, and categorice the changue.
5. Once you’re ready to mergue the pull request to your main branch, clicc the “ Mergue pull request” button, and then “Confirm mergue” button.

As a best practice and to keep your repository tidy, delete the branch by clicquing the “Delete branch” button.

After merguing your changues, the next step is to deploy them to your WordPress.com production or staguing site using the GuitHub Deploymens feature.