As a developer, I should be able to easily get and apply patches from trac

[jorbin]

getting and applying patches from core.trac.wordpress.org can be a bit of a hassle. Find the ticket, look at the patch, scroll to the bottom. Download the original. What if it was as easy as entering a trac url? or ticket number? Or the not raw patch url?

That is what this aims to solve.

To use:

grunt patch # This will look for patches in your root checkout
grunt patch:18380 # This will look for patches on ticket 18380 and let you choose which one to install
grunt patch:https://core.trac.wordpress.org/ticket/18380 # same as above
grunt patch:https://core.trac.wordpress.org/attachment/ticket/18380/18380.4.diff # Will download and apply that specific patch

[jorbin]

spaces, not tabs (fml)

[nacin]

This is awesome.

When asking for all patches for a ticket, it would be awesome if it could show you the author of the patch and the relative time since it was uploaded (as Trac shows). I'm trying to do it myself but my JS regex-fu is a little weak today.

[Denis-de-Bernardy]

Replying to nacin:

This is awesome.

It's also a dup of #9724, which I never understood why you closed as workforme.

[jorbin]

Replying to nacin:

When asking for all patches for a ticket, it would be awesome if it could show you the author of the patch and the relative time since it was uploaded (as Trac shows). I'm trying to do it myself but my JS regex-fu is a little weak today.

Agreed. Also, Done. Also included the size of the patch.

[bassgang]

First usage looks fine for me, will try to use it more in future.

[jorbin]

We will need to update

​http://make.wordpress.org/core/handbook/working-with-patches/patches-with-command-line/

when/if this is committed.

[SergeyBiryukov]

Replying to Denis-de-Bernardy:

It's also a dup of #9724, which I never understood why you closed as workforme.

If I had to guess, it's because build tools didn't belong to the core repository at the time. However, you could always add them to relevant Codex pages.

[jorbin]

Fixed a bug where only having one patch|diff in your directory caused patching to fail. Thanks @nacin for the report.

Also updated some spacing, grammar, and wording of the instructions. Thanks @nacin @evarlese and @helen

[nacin]

In 27299:

Developer tools: grunt-patch-wordpress from jorbin, for applying patches directly from Trac.

Mapped to grunt patch, which declares usage. Requires npm install to install.

props jorbin. props helen, evarlese for help with grammar/instructions.
see #27023.

[helen]

Noticing a couple things:

• If I apply a patch that was done within /src or before /src, it fails - I think it should be smart about it the same way it does for the other way around (which does work).
• I'd also want to see successfully modified files.

[jorbin]

Replying to helen:

• If I apply a patch that was done within /src or before /src, it fails - I think it should be smart about it the same way it does for the other way around (which does work).

This is tracked at ​https://github.com/aaronjorbin/grunt-patch-wordpress/issues/3 I'm going to start working on adding it next week.

• I'd also want to see successfully modified files.

I like this idea. Thanks!

[nacin]

As the library continues to improve, we can start to incorporate this into our documentation for sure.

[nacin]

In 27721:

Update grunt-patch-wordpress to 0.2.0.

props jorbin, yoavf, sabreuse.
see #27023.

[nacin]

In 27848:

Update grunt-patch-wordpress to 0.2.1 which applies patches with a/ b/ paths.

props jorbin.
see #27023.