Screenshot of Grunt Patch WordPress from the command line

Future of Grunt Patch WordPress

I’ve had some extra time on my hand recently and while I am not quite ready to start looking for full-time work, I have been thinking about code recently and I’m back to thinking about the contribution process to WordPress. Grunt Patch WordPress is a tool that helps people contribute code to WordPress and that I estimate has saved many hours for contributors.

Grunt Patch WordPress started as a standardization of some helpers for interacting with Trac. I knew about a ruby script that Mark Jaquith was using along with some bash scripts Nacin had. This was around when WordPress first switched to having a public build process so it was time.

Patches to WordPress come in many shapes and sizes. They can be generated from SVN or GIT. They can come from the build repository or the develop repository. They can become stale due to files being moved. They can be set up as PRs on GitHub. Grunt Patch WordPress takes care of all of this so developers of WordPress can focus on the content of the patch and not the details of how it was created.

Despite working well and saving hundreds of hours since it was introduced in nine years ago, there are areas of improvement that I think would help improve the tool.

Changes I would like to make

1. Save passwords to keychains

Right now, the patch uploading is a bit more difficult than it needs to be. If Passwords and Usernames could be securely stored, this would save a little bit of time each time someone wants to upload a patch.

2. Better Github Intgration

Right now you can manually enter a GitHub PR and it will apply it as a patch. However, the patches aren’t listed when selecting them by just entering a ticket number. As more contributors work on GitHub, this is becoming more and more important.

3. Code Modernization

Right now there are outdated libraries used. Additionally, nine years ago things like promises were in their infancy. I would like to improve the code in general so it’s easier for more developers to work with Grunt Patch WordPress.

Want to help Grunt Patch WordPress?

As the original author and primary maintainer, I think I am in the best position to make these changes. If you are interested in sponsoring this work to help people contribute to WordPress, please get in touch. I’m also considering Github Sponsors as a way to help crowdsource funding to support these changes.


12 responses to “Future of Grunt Patch WordPress”

  1. This tool is so helpful when working on or testing patches. It really eased the process for me when I started contributing more seriously. And I didn’t know it could also be used to upload patches. Happy to help in any way make it even better !

  2. Thanks! Glad to hear it’s something that has helped you out 🙂 Right now you can do it with ` grunt upload_patch:20000` but you need to enter your credentials each time

  3. I’ll give it a try next time !

  4. Future of Grunt Patch WordPress…

  5. I just made the decision to start using GitHub Sponsors with the idea of trying to support my contributions to WordPress. While I am still looking for my next full-time position, I’ve been enjoying contributing to WordPress and wanted to see if the community would support those contributions. Some of what I hope to be […]

Leave a Reply

Only people in my network can comment.
%d bloggers like this: