Contents
Overview #
Once you’ve edited the file and tested it, you need to create the patch so other people can test it as well. You can create a patch a number of ways.
Windows #
If you are on Windows, consider using Tortoise SVN. You can read our tutorial on creating a patch with Tortoise SVN..
Mac/Linux Command Line #
Make a patch, for filename.php:
$ svn diff filename.php > filename.diff
Make a patch for all files modified in the checkout:
$ svn diff > big_patch.diff
Apply a patch from someone else:
$ patch -p0 < patch.diff
There are some GUI options for the Mac, as well — you just need it to create patch files (Versions cannot, for example).
Also: creating SVN patches using Git, from Cristi Burca.
andrewspittle 11:35 pm on August 5, 2012 Permalink | Log in to Reply
This is probably worth reading through in order to flesh this list out.
http://codex.wordpress.org/User:HEngel/How_To_Become_A_WordPress_Developer
inderpreet99 2:07 pm on August 9, 2012 Permalink | Log in to Reply
There are 3 links to Mozilla/Firefox that should be replaced by WordPress-equivalent.
Replace: Picking bugs to work on: https://developer.mozilla.org/en/Hacking_Firefox
With: Picking bugs to work on: http://core.trac.wordpress.org/report
Replace: Knowing where to ask for help: https://developer.mozilla.org/en/Hacking_Firefox
with: Knowing where to ask for help: (forum? IRC?)
Andrew Nacin 8:37 pm on August 11, 2012 Permalink | Log in to Reply
I found those Mozilla pages in my research and I want them to inspire us as a good model. To put it another way, I don’t think our current equivalents are good enough.
Siobhan 9:58 pm on October 18, 2012 Permalink | Log in to Reply
I wrote a guide to contributing to WP using Github for Mac: https://docs.google.com/a/wordsforwp.com/document/d/16Hzc0_Z1c8VSMJplAk4dcBter3ntlfVeyyCO56VANA4/edit
Would like to contribute it to the manual but not sure how. cc @ipstenu @andrewspittle
John Blackbourn (johnbillion) 10:13 am on November 26, 2012 Permalink | Log in to Reply
Do we have a page (or section) anywhere yet which mentions that trivial patches that *only* fix coding standards are discouraged?
Sergey Biryukov 11:27 am on January 3, 2013 Permalink | Log in to Reply
http://make.wordpress.org/core/2011/03/23/code-refactoring/
Daniel Bachhuber 12:45 am on January 6, 2013 Permalink | Log in to Reply
Couple of things:
Eric Andrew Lewis 3:29 pm on April 8, 2013 Permalink | Log in to Reply
Agree on the first point, came here to make that comment
advancement to excellence: How To Become A Top WordPress Developer | ShadesColour & Associates 4:35 am on January 10, 2013 Permalink | Log in to Reply
[...] the Core Contributor handbook and learn how to submit a patch. It can be a daunting process your first time around, but look for a challenge that you can tackle, [...]
Docs Chat 17th January « Make WordPress Documentation 10:59 pm on January 17, 2013 Permalink | Log in to Reply
[...] – I shared the spreadsheet with the of the current content. We agreed that pages such as Submitting a Patch are in dire need of help. There should be information so that non-coders know how to make a [...]
How To Become A Top WordPress Developer - Goodfav Howto 9:55 pm on March 2, 2013 Permalink | Log in to Reply
[...] the Core Contributor handbook and learn how to submit a patch. It can be a daunting process your first time around, but look for a challenge that you can tackle, [...]