Applying a patch to a module

Drupal: 9m
Information

This video goes through the process of finding a patch from the Drupal.org issue queue, and then applying it to a contributed module. After testing the patch and confirming that it fixes the bug, we then walk through the process of reporting back that the patch has been reviewed and tested by the community and is ready to be applied to the module's main branch. This video will show you how to clone a Drupal.org project, but it assumes that you already have git installed and are familiar with the basics of using git.

Here's more information on how to set up your command line to show the git branch release context.

For instructions on creating a patch and submitting it to Drupal.org, watch the Creating a patch for a module video.

Discussion

Comments on this video

You need to be an active subscriber to comment. or .

Shouldn't you take a look at how the patch fixes the issue before changing the issue status to rtbc?

Sure that's always a good idea. In the video I said to mark it RTBC simply because it fixed the problem. But checking out what code was actually applied, reviewing the actual lines of code, might reveal some sort of bad practice performance-wise or perhaps coding standard-wise.

Thank you for pointing that out!

Lullabot logo

Lullabot has trained thousands of Drupal developers & guided the development of some of the largest Drupal websites.