Drupal Association members fund grants that make connections all over the world.
Last updated May 15, 2015.
On this page:
- Skills needed
- Detailed steps
- Background and reference information
- Next steps: moving beyond this task
- Notes for reviewers
To get help completing this task, see the Getting help completing your task page.
Add a "patch" (software fix) to an issue in the Drupal Core project.
- If you don't have a Drupal site to test on, set up a local server. You probably do not want to use a live, production web site for this task.
- Install Git on your computer, if it is not already installed. See the installing git page for more information.
- Do update drupal core repository through git before start working on any new issue.
- Find issues for Drupal core.
- Follow the steps in the Novice code contributors guide to find an issue, make a patch (and interdiff), and attach the patch to an issue
Background and reference information
- Git handbook (Git is the version control system that the Drupal project uses)
- Drupal project coding standards
- Drupal project code documentation standards
- List of additional resources for Drupal programming
Next steps: moving beyond this task
- Fix more issues in the Drupal Core project, following the same steps as above.
- Find issues in other projects and fix them. To do that, go to the project page for a contributed module or theme that you use, and click the Issues link in the sidebar of the page. Then follow the same steps to supply patches.
- Follow notes for reviewers and review someone elses work for the same task type.
Notes for reviewers
The documentation above is for someone new to doing the task.
Specific to this task:
- Patches for bugfixes should be uploaded with a test-only patch followed by a combined test + fix patch.
- Updates to earlier patches should be accompanied by an interdiff.
- Review the patch in terms of the core gates.
- See xjm's patch review checklist (archive.org).
- Your review should be constructive and encouraging.