{"id":13656776,"url":"https://github.com/zendtech/php-src","last_synced_at":"2025-04-24T00:32:07.523Z","repository":{"id":27924791,"uuid":"31417057","full_name":"zendtech/php-src","owner":"zendtech","description":"The PHP Interpreter","archived":false,"fork":true,"pushed_at":"2019-03-28T14:52:18.000Z","size":349360,"stargazers_count":385,"open_issues_count":0,"forks_count":37,"subscribers_count":62,"default_branch":"jit-dynasm","last_synced_at":"2024-11-10T10:39:03.381Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://www.php.net","language":"C","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"php/php-src","license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/zendtech.png","metadata":{"files":{"readme":"README.GIT-RULES","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-02-27T11:48:08.000Z","updated_at":"2024-10-31T23:26:54.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/zendtech/php-src","commit_stats":null,"previous_names":[],"tags_count":100,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/zendtech%2Fphp-src","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/zendtech%2Fphp-src/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/zendtech%2Fphp-src/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/zendtech%2Fphp-src/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/zendtech","download_url":"https://codeload.github.com/zendtech/php-src/tar.gz/refs/heads/jit-dynasm","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250539529,"owners_count":21447328,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-02T05:00:32.115Z","updated_at":"2025-04-24T00:32:02.510Z","avatar_url":"https://github.com/zendtech.png","language":"C","funding_links":[],"categories":["C (61)"],"sub_categories":[],"readme":"====================\n  Git Commit Rules\n====================\n\nThis is the first file you should be reading when contributing code via Git.\nWe'll assume you're basically familiar with Git, but feel free to post\nyour questions on the mailing list. Please have a look at\nhttp://git-scm.com/ for more detailed information on Git.\n\nPHP is developed through the efforts of a large number of people.\nCollaboration is a Good Thing(tm), and Git lets us do this. Thus, following\nsome basic rules with regards to Git usage will::\n\n   a. Make everybody happier, especially those responsible for maintaining\n      PHP itself.\n\n   b. Keep the changes consistently well documented and easily trackable.\n\n   c. Prevent some of those 'Oops' moments.\n\n   d. Increase the general level of good will on planet Earth.\n\nHaving said that, here are the organizational rules::\n\n   1. Respect other people working on the project.\n\n   2. Discuss any significant changes on the list before committing and get\n      confirmation from the release manager for the given branch.\n\n   3. Look at EXTENSIONS file to see who is the primary maintainer of\n      the code you want to contribute to.\n\n   4. If you \"strongly disagree\" about something another person did, don't\n      start fighting publicly - take it up in private email.\n\n   5. If you don't know how to do something, ask first!\n\n   6. Test your changes before committing them. We mean it. Really.\n      To do so use \"make test\".\n\n   7. For development use the --enable-debug switch to avoid memory leaks\n      and the --enable-zts switch to ensure your code handles\n      TSRM correctly and doesn't break for those who need that.\n\nCurrently we have the following branches in use::\n\n  master    Active development branch for PHP 8.0, which is open for\n            backwards incompatible changes and major internal API changes.\n\n  PHP-7.4   Active development branch for PHP 7.4, which is open for\n            new features and minor internal API changes.\n\n  PHP-7.3   Is used to release the PHP 7.3.x series. This is a current\n            stable version and is open for bugfixes only.\n\n  PHP-7.2   Is used to release the PHP 7.2.x series. This is a current\n            stable version and is open for bugfixes only.\n\n  PHP-7.1   Is used to release the PHP 7.1.x series. This is an old\n            stable version and is open for security fixes only.\n\n  PHP-7.0   This branch is closed.\n\n  PHP-5.6   This branch is closed.\n\n  PHP-5.5   This branch is closed.\n\n  PHP-5.4   This branch is closed.\n\n  PHP-5.3   This branch is closed.\n\n  PHP-5.2   This branch is closed.\n\n  PHP-5.1   This branch is closed.\n\n  PHP-4.4   This branch is closed.\n\n  PHP-X.Y.Z These branches are used for the release managers for tagging\n            the releases, hence they are closed to the general public.\n\nThe next few rules are more of a technical nature::\n\n   1. All non-security bugfix changes should first go to the lowest bugfix\n      branch (i.e. 7.2) and then get merged up to all other branches.\n      All security fixes should go to the lowest security fixes branch (i.e 5.6).\n      If a change is not needed for later branches (i.e. fixes for features\n      which were dropped from later branches) an empty merge should be done.\n\n   2. All news updates intended for public viewing, such as new features,\n      bug fixes, improvements, etc., should go into the NEWS file of *any\n      stable release* version with the given change. In other words,\n      news about a bug fix which went into PHP-5.4, PHP-5.5 and master\n      should be noted in both PHP-5.4/NEWS and PHP-5.5/NEWS but\n      not master, which is not a public released version yet.\n\n   3. Do not commit multiple files and dump all messages in one commit. If you\n      modified several unrelated files, commit each group separately and\n      provide a nice commit message for each one. See example below.\n\n   4. Do write your commit message in such a way that it makes sense even\n      without the corresponding diff. One should be able to look at it, and\n      immediately know what was modified. Definitely include the function name\n      in the message as shown below.\n\n   5. In your commit messages, keep each line shorter than 80 characters. And\n      try to align your lines vertically, if they wrap. It looks bad otherwise.\n\n   6. If you modified a function that is callable from PHP, prepend PHP to\n      the function name as shown below.\n\n\nThe format of the commit messages is pretty simple.\n\n\u003cmax 79 characters short description\u003e\\n\n\\n\n\u003clong description, 79 chars per line\u003e\n\\n\n\nAn Example from the git project (commit 2b34e486bc):\n\npack-objects: Fix compilation with NO_PTHREDS\n\nIt looks like commit 99fb6e04 (pack-objects: convert to use\nparse_options(), 2012-02-01) moved the #ifdef NO_PTHREDS around but\nhasn't noticed that the 'arg' variable no longer is available.\n\nIf you fix some bugs, you should note the bug ID numbers in your\ncommit message. Bug ID should be prefixed by \"#\" for easier access to\nbug report when developers are browsing CVS via LXR or Bonsai.\n\nExample:\n\nFixed bug #14016 (pgsql notice handler double free crash bug.)\n\nWhen you change the NEWS file for a bug fix, then please keep the bugs\nsorted in decreasing order under the fixed version.\n\nYou can use OpenGrok (http://lxr.php.net/) and gitweb (http://git.php.net/)\nto look at PHP Git repository in various ways.\n\n\nFor further information on the process and further details please refer to\nhttps://wiki.php.net/vcs/gitworkflow and https://wiki.php.net/vcs/gitfaq\n\nHappy hacking,\n\nPHP Team\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fzendtech%2Fphp-src","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fzendtech%2Fphp-src","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fzendtech%2Fphp-src/lists"}