Title: Developer best practices
Author: WordPress VIP Documentation
Published: March 10, 2026

---

 1. [Guidebooks](https://docs.wpvip.com/guidebooks/)
 2. Developer best practices

#  Developer best practices

![](https://docs.wpvip.com/wp-content/uploads/sites/2/2025/11/guidebooks-5-dev-best-
practices.png)

When developers follow best practices for developing code, collaboration improves
and your team can work more effectively.

[Quickstart](https://docs.wpvip.com/guidebooks/developer-best-practices/github-pull-request-flow/)

---

## Overview

##  GitHub pull request flow

To streamline code reviews and deployments for their team, it is strongly recommended
that all developers on the VIP Platform use the GitHub pull request flow.

##  GitHub flow on the VIP Platform

The infrastructure of the VIP Platform is built to support a “Code moves up; content
moves down” development workflow (e.g. **develop** → **production** for code development).

##  Create a good commit message

Commit messages are one of the most common ways that developers communicate with
each other. As part of the GitHub flow, it is important that commit messages are
informative and clearly written.

##  Create a good changeset

Changesets are the heart of any version control system, and making good changesets
is important to the maintainability of a codebase.

##  Prepare code for review

Code review from other internal team members is a valuable part of the development
workflow. By following these guidelines, reviews and feedback can be more quickly
received, and a pull request can be more quickly approved.

##  Contribute to WordPress Core

The WordPress.org open source community is comprised of talented individuals around
the world. This community is always interested in receiving additional help from
new contributors. Developers who support enterprise sites on the VIP Platform can
lend a unique voice to WordPress that helps improve the project for all.

Last updated: March 10, 2026