Contributing to PHP

Anybody who programs in PHP can be a contributing member of the community that develops and deploys it; the task of deploying PHP, documentation and associated websites is a never-ending one. With every release or release candidate comes a wave of work, which takes a lot of organization and co-ordination.

You don't need any special access to download, build, debug and begin submitting PHP or PECL code, tests or documentation. Once you've followed this guide and had several contributions accepted, commit privileges are often quickly granted.

Index

Pull requests
Filing bugs
Feature requests
Technical resources
Writing tests
Writing documentation
Getting help
PHP source code directory structure
PHP internals
PECL extensions
Checklist for submitting contribution
What happens after submitting contribution?
What happens when your contribution is applied?
Git commit rules
Copyright and license headers
NEWS file

Pull requests

PHP welcomes pull requests to add tests, fix bugs and to implement RFCs. Please be sure to include tests as appropriate!

By submitting a pull request, you certify that you have the necessary rights to submit the work, that the work does not violate any third-party rights (including those of your employer, if applicable), and that you license your contribution under the PHP License or under another license if explicitly accepted by the PHP project maintainers.

If you are fixing a bug, then please submit your PR against the lowest actively supported branch of PHP that the bug affects (only green branches on the supported version page are supported). For example, at the time of writing, the lowest supported version is PHP 8.0, which corresponds to the PHP-8.0 branch in Git. Please also make sure you add a link to the PR in the bug on the bug tracker or the old bug tracker.

Pull requests implementing RFCs should be submitted against master.

Pull requests should never be submitted against PHP-x.y.z branches, as these are only used for release management.

If your pull request exhibits conflicts with the base branch, please resolve them by using git rebase instead of git merge.

Fork the official PHP repository and send a pull request. A notification will be sent to the pull request mailing list. Sending a note to PHP Internals list (internals@lists.php.net) may help getting more feedback and quicker turnaround. You can also add pull requests to bug reports and old bug reports.

Read Git access page for help on using Git to get and build PHP source code. We recommend to look at our workflow and our FAQ.

Filing bugs

Bugs can be filed on GitHub Issues. If this is the first time you've filed a bug, we suggest reading the guide to reporting a bug.

Where possible, please include a self-contained reproduction case!

Feature requests

Feature requests are generally submitted in the form of Requests for Comments (RFC), ideally accompanied by pull requests. You can find the extremely large list of RFCs that have been previously considered on the PHP Wiki.

To create an RFC, discuss it with the extension maintainer, and discuss it on the development mailing list internals@lists.php.net. RFC Wiki accounts can be requested on https://wiki.php.net/start?do=register. PHP extension maintainers can be found in the EXTENSIONS file in the PHP source code repository. Mailing list subscription is explained on the mailing lists page.

You may also want to read The Mysterious PHP RFC Process for additional notes on the best way to approach submitting an RFC.

Technical resources

There are a number of technical resources on php-src. Unfortunately, they are scattered across different websites, and often outdated. Nonetheless, they can provide a good starting point for learning about the fundamentals of the code base.

https://www.phpinternalsbook.com/
https://www.npopov.com/
https://wiki.php.net/internals
- Objects
https://qa.php.net/
https://phpinternals.net/
- Implementing new operator, part 2
- Opcode extending

Writing tests

We love getting new tests! PHP is a huge project and improving test coverage is a huge win for every PHP user.

Our QA site includes a page detailing how to write test cases.

Submitting test scripts helps us to understand what functionality has changed. It is important for the stability and maintainability of PHP that tests are comprehensive.

Failure conditions of zend_parse_parameters, ZEND_PARSE_PARAMETERS() and similar functions should not be tested. These parameter parsing APIs are already extensively tested, and additional tests only complicate future modifications.

For newly created tests, a --CREDITS-- section should no longer be included, as test authorship is already accurately tracked by Git. If multiple authors should be credited, the Co-authored-by tag in the commit message may be used.

Writing documentation

Editing the manual is done by checking out the XML sources using Git and editing and building it per the instructions on the documentation site.

Getting help

If you are having trouble contributing to PHP, or just want to talk to a human about what you're working on, you can contact us via the internals mailing list, or the documentation mailing list for documentation issues.

Although not a formal channel, you can also find a number of core developers on the #php.pecl channel on EFnet. Similarly, many documentation writers can be found on #php.doc. Windows development IRC channel is available at #winphp-dev on FreeNode.

PHP source code directory structure

PHP source code also includes several files generated during development and several parts where maintenance is happening upstream in their respective locations.

<php-src>/
 ├─ .git/                           # Git configuration and source directory
 ├─ TSRM/                           # Thread Safe Resource Manager
 └─ Zend/                           # Zend Engine
    ├─ asm/                         # Bundled from src/asm in https://github.com/boostorg/context
    ├─ zend_vm_execute.h            # Generated by `Zend/zend_vm_gen.php`
    ├─ zend_vm_opcodes.c            # Generated by `Zend/zend_vm_gen.php`
    ├─ zend_vm_opcodes.h            # Generated by `Zend/zend_vm_gen.php`
    └─ ...
 └─ build/                          # *nix build system files
    ├─ ax_*.m4                      # https://github.com/autoconf-archive/autoconf-archive
    ├─ config.guess                 # https://git.savannah.gnu.org/cgit/config.git
    ├─ config.sub                   # https://git.savannah.gnu.org/cgit/config.git
    ├─ libtool.m4                   # https://git.savannah.gnu.org/cgit/libtool.git
    ├─ ltmain.sh                    # https://git.savannah.gnu.org/cgit/libtool.git
    ├─ pkg.m4                       # https://gitlab.freedesktop.org/pkg-config/pkg-config
    ├─ shtool                       # https://www.gnu.org/software/shtool/
    └─ ...
 ├─ docs/                           # PHP internals and repository documentation
 └─ ext/                            # PHP core extensions
    └─ bcmath/
       ├─ libbcmath/                # Forked and maintained in php-src
       └─ ...
    └─ curl/
       ├─ sync-constants.php        # The curl symbols checker
       └─ ...
    └─ date/
       └─ lib/                      # Bundled datetime library https://github.com/derickr/timelib
          ├─ parse_date.c           # Generated by re2c 0.15.3
          ├─ parse_iso_intervals.c  # Generated by re2c 0.15.3
          └─ ...
       └─ ...
    └─ ffi/
       ├─ ffi_parser.c              # Generated by https://github.com/dstogov/llk
       └─ ...
    └─ fileinfo/
       ├─ libmagic/                 # Modified libmagic https://github.com/file/file
       ├─ data_file.c               # Generated by `ext/fileinfo/create_data_file.php`
       ├─ libmagic.patch            # Modifications patch from upstream libmagic
       ├─ magicdata.patch           # Modifications patch from upstream libmagic
       └─ ...
    └─ gd/
       ├─ libgd/                    # Bundled and modified GD library https://github.com/libgd/libgd
       └─ ...
    └─ mbstring/
       ├─ libmbfl/                  # Forked and maintained in php-src
       ├─ unicode_data.h            # Generated by `ext/mbstring/ucgendat/ucgendat.php`
       └─ ...
    └─ opcache/
       └─ jit/
          └─ ir/                    # Bundled part of IR framework https://github.com/dstogov/ir
    └─ pcre/
       ├─ pcre2lib/                 # https://www.pcre.org/
       └─ ...
    └─ skeleton/                    # Skeleton for developing new extensions with `ext/ext_skel.php`
       └─ ...
    └─ standard/
       └─ html_tables/
          ├─ mappings/              # https://www.unicode.org/Public/MAPPINGS/
          └─ ...
       ├─ credits_ext.h             # Generated by `scripts/dev/credits`
       ├─ credits_sapi.h            # Generated by `scripts/dev/credits`
       ├─ html_tables.h             # Generated by `ext/standard/html_tables/html_table_gen.php`
       └─ ...
    └─ tokenizer/
       ├─ tokenizer_data.c          # Generated by `ext/tokenizer/tokenizer_data_gen.sh`
       └─ ...
    └─ zend_test                    # For testing internal APIs. Not needed for regular builds.
       └─ ...
    └─ zip/                         # Bundled https://github.com/pierrejoye/php_zip
       └─ ...
    └─ ...
 └─ main/                           # Binding that ties extensions, SAPIs, and engine together
    ├─ streams/                     # Streams layer subsystem
    ├─ php_version.h                # Generated by release managers using `configure`
    └─ ...
 ├─ pear/                           # PEAR installation
 └─ sapi/                           # PHP SAPI modules
    └─ cli/
       ├─ mime_type_map.h           # Generated by `sapi/cli/generate_mime_type_map.php`
       └─ ...
    └─ ...
 ├─ scripts/                        # php-config, phpize and internal development scripts
 ├─ tests/                          # Core features tests
 └─ win32/                          # Windows build system files
    ├─ cp_enc_map.c                 # Generated by `win32/cp_enc_map_gen.exe`
    └─ ...
 └─ ...

PHP internals

For information on PHP internal C functions see References about Maintaining and Extending PHP. Various external resources can be found on the web. A standard printed reference is the book "Extending and Embedding PHP" by Sara Golemon.

PECL extensions

If you are fixing broken functionality in a PECL extension then create a bug or identify an existing bug at bugs.php.net. A bug can be used to track the change progress and prevent your changes getting lost in the PHP mail archives. Some PECL extensions have their own bug tracker locations and different contributing procedures.

If your change is large then create a Request for Comments (RFC), discuss it with the extension maintainer, and discuss it on the development mailing list pecl-dev@lists.php.net depending on the extension. PECL mailing list subscription is explained on the PECL support page.

Update any open bugs and add a link to the source of your change. Send the patch or pointer to the bug to pecl-dev@lists.php.net. Also CC the extension maintainer. Explain what has been changed by your patch. Test scripts should be included.

Checklist for submitting contribution

Read Coding standards before you start working.
Update git source just before running your final diff and before testing.
Add inline comments and/or have external documentation ready. Use only /* */ style comments, not //.
Create test scripts for use with make test.
Run make test to check your change doesn't break other features.
Rebuild PHP with --enable-debug which will show some kinds of memory errors and check the PHP and web server error logs after running your PHP tests.
Rebuild PHP with --enable-zts to check your change compiles and operates correctly in a thread-safe PHP.
Review the change once more just before submitting it.

What happens after submitting contribution?

If your change is easy to review and obviously has no side-effects, it might be committed relatively quickly.

Because PHP is a volunteer-driven effort, more complex changes will require patience on your side. If you do not receive feedback in a few days, consider bumping. Before doing this think about these questions:

Did I send the patch to the right mailing list?
Did I review the mailing list archives to see if these kind of changes had been discussed before?
Did I explain my change clearly?
Is my change too hard to review? If so, why?

What happens when your contribution is applied?

Your name will likely be included in the Git commit log. If your change affects end users, a brief description and your name might be added to the NEWS file.

Git commit rules

This section refers to contributors that have Git push access and make commit changes themselves. We'll assume you're basically familiar with Git, but feel free to post your questions on the mailing list. Please have a look at the more detailed information on Git.

PHP is developed through the efforts of a large number of people. Collaboration is a Good Thing(tm), and Git lets us do this. Thus, following some basic rules with regard to Git usage will:

Make everybody happier, especially those responsible for maintaining PHP itself.
Keep the changes consistently well documented and easily trackable.
Prevent some of those 'Oops' moments.
Increase the general level of good will on planet Earth.

Having said that, here are the organizational rules:

Respect other people working on the project.
Discuss any significant changes on the list before committing and get confirmation from the release manager for the given branch.
Look at EXTENSIONS file to see who is the primary maintainer of the code you want to contribute to.
If you "strongly disagree" about something another person did, don't start fighting publicly - take it up in private email.
If you don't know how to do something, ask first!
Test your changes before committing them. We mean it. Really. To do so use make test.
For development use the --enable-debug switch to avoid memory leaks and the --enable-zts switch to ensure your code handles TSRM correctly and doesn't break for those who need that.

Currently, we have the following branches in use:

Branch
master	Active development branch for PHP 8.6, which is open for backwards incompatible changes and major internal API changes.
PHP-8.5	Is used to release the PHP 8.5.x series. This is a current stable version and is open for bugfixes only.
PHP-8.4	Is used to release the PHP 8.4.x series. This is a current stable version and is open for bugfixes only.
PHP-8.3	Is used to release the PHP 8.3.x series. This is a current stable version and is open for bugfixes only.
PHP-8.2	Is used to release the PHP 8.2.x series. This is an old stable version and is open for security fixes only.
PHP-8.1	Is used to release the PHP 8.1.x series. This is an old stable version and is open for security fixes only.
PHP-8.0	This branch is closed.
PHP-7.4	This branch is closed.
PHP-7.3	This branch is closed.
PHP-7.2	This branch is closed.
PHP-7.1	This branch is closed.
PHP-7.0	This branch is closed.
PHP-5.6	This branch is closed.
PHP-5.5	This branch is closed.
PHP-5.4	This branch is closed.
PHP-5.3	This branch is closed.
PHP-5.2	This branch is closed.
PHP-5.1	This branch is closed.
PHP-4.4	This branch is closed.
PHP-X.Y.Z	These branches are used for the release managers for tagging the releases, hence they are closed to the general public.

The next few rules are more of a technical nature:

All non-security bugfix changes should first go to the lowest bugfix branch (i.e. 8.0) and then get merged up to all other branches. All security fixes should go to the lowest security fixes branch (i.e 7.4). If a change is not needed for later branches (i.e. fixes for features which were dropped from later branches) an empty merge should be done.
All news updates intended for public viewing, such as new features, bug fixes, improvements, etc., should go into the NEWS file. See the section on NEWS below.
Do not commit multiple files and dump all messages in one commit. If you modified several unrelated files, commit each group separately and provide a nice commit message for each one. See example below.
Do write your commit message in such a way that it makes sense even without the corresponding diff. One should be able to look at it, and immediately know what was modified. Definitely include the function name in the message as shown below.
In your commit messages, keep each line shorter than 80 characters. And try to align your lines vertically, if they wrap. It looks bad otherwise.
If you modified a function that is callable from PHP, prepend PHP to the function name as shown below.

The format of the commit messages is pretty simple.

<max 79 characters short description>\n
\n
<long description, 79 chars per line>
\n

An Example from the git project (commit 2b34e486bc):

pack-objects: Fix compilation with NO_PTHREDS

It looks like commit 99fb6e04 (pack-objects: convert to use parse_options(),
2012-02-01) moved the #ifdef NO_PTHREDS around but hasn't noticed that the
'arg' variable no longer is available.

If you fix some bugs, you should note the bug ID numbers in your commit message.

Example:

Fixed GH-14009: Fix prototype for trait method.

When you change the NEWS file for a bug fix, then please keep the bugs sorted under the fixed version.

Copyright and license headers

New source code files should include the following header block:

/*
  +----------------------------------------------------------------------+
  | Copyright (c) The PHP Group                                          |
  +----------------------------------------------------------------------+
  | This source file is subject to version 3.01 of the PHP license,      |
  | that is bundled with this package in the file LICENSE, and is        |
  | available through the world-wide-web at the following url:           |
  | https://www.php.net/license/3_01.txt                                 |
  | If you did not receive a copy of the PHP license and are unable to   |
  | obtain it through the world-wide-web, please send a note to          |
  | license@php.net so we can mail you a copy immediately.               |
  +----------------------------------------------------------------------+
  | Author:                                                              |
  +----------------------------------------------------------------------+
*/

NEWS

The purpose of the NEWS file is to record all the changes that are relevant for users and developers alike. These could be bug fixes, feature additions, syntax additions, or deprecations.

Format

Each PHP version has a section, starting with the format:

{DD} {MMM} {YYY}, PHP {version}

Such as:

06 Jun 2024, PHP 8.1.29

In each section, entries are ordered by their extension. Extensions are listed alphabetically, with the exception of "Core", which MUST be listed first. Each extension's section starts with: - {name}:\n

For each extension, entries are indented by two spaces, followed by . (a period and a space).

Entries MUST start with a capital and end with a period (.). The period goes outside of the {issue-description}.

Each entry SHOULD be followed by the name of the contributor, their php.net account name, or their GitHub handle if they so choose.

Entries MUST be wrapped at 80 characters.

If an entry pertains a bug fix, they MUST be formatted as:

Fixed bug GH-{number} ({issue-description}). ({contributor})

Bug fix entries SHOULD be clustered together, and ordered according to their issue number. The {issue-description} SHOULD represent what the actual bug fix is about, and not necessarily what the user reported. Edit the description in the GitHub ticket to match.

On the rare occasion where a bug from our deprecated bug system is fixed, the entry MUST be formatted as:

Fixed bug #{number} ({issue-description}). ({contributor})

An example:

31 Jul 2025, PHP 8.5.0alpha4

- Core:
  . Added PHP_BUILD_PROVIDER constant. (timwolla)
  . Fixed bug GH-16665 (\array and \callable should not be usable in
    class_alias). (nielsdos)
  . Fixed bug GH-19326 (Calling Generator::throw() on a running generator with
    a non-Generator delegate crashes). (Arnaud)

- OPcache:
  . Make OPcache non-optional. (Arnaud, timwolla)

- OpenSSL:
  . Add $digest_algo parameter to openssl_public_encrypt() and
    openssl_private_decrypt() functions. (Jakub Zelenka)

Branches

Depending on what sort of fix it is, or where in the release cycle we are, different NEWS files must be updated.

Security fixes: In the lowest security-supported branch which received the security fix, and in each newer branch, except for master unless alpha releases have been tagged, and a release branch has not been created.

Bug fixes: In the lowest supported branch, and in each newer branch, except for master unless alpha releases have been tagged, and a release branch has not been created.

Feature additions: In master only.

If for some reason a feature is introduced in a branch lower than master, although this is strictly prohibited by other policies, then the entry must also be in master.

Thanks

Thank you for contributing to PHP!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!