Patch submission guidelines
From Joomla! Documentation
(Difference between revisions)
(New page: {{review}} We're always grateful for patches to Joomla's code. Indeed, bug reports with associated patches will get fixed far more quickly than those without patches. '''Patch style''' ...) |
|||
| Line 10: | Line 10: | ||
* Name the patch file with a .diff extension | * Name the patch file with a .diff extension | ||
* Put the prefix "[patch] " before the title of your artefact. This will make it obvious that the artefact includes a patch. | * Put the prefix "[patch] " before the title of your artefact. This will make it obvious that the artefact includes a patch. | ||
| + | * [[Learn more about patch files]] | ||
Revision as of 14:44, 17 June 2008
 |
This is a article which: needs review. You can help the Joomla! Documentation Wiki by contributing to it. More pages that need help similar to this one are here. If you feel the need is satistified, please remove this notice. While actively editing, consider adding {{inuse}} to reduce edit conflicts. |
We're always grateful for patches to Joomla's code. Indeed, bug reports with associated patches will get fixed far more quickly than those without patches.
Patch style
- Make sure your code matches our coding style.
- Submit patches in the format returned by the svn diff command. An exception is for code changes that are described more clearly in plain English than in code. Indentation is the most common example; it's hard to read patches when the only difference in code is that it's indented.
- Attach patches to a artefact in the trackers, using the "attach file" button. Please don't put the patch in the artefact description or comment unless it's a single line patch.
- Name the patch file with a .diff extension
- Put the prefix "[patch] " before the title of your artefact. This will make it obvious that the artefact includes a patch.
- Learn more about patch files
