Project maintainers can spend a lot of time understanding the details of an issue and reproducing reported bugs. By confirming that a bug can be reproduced and improving/writing issue summaries, you help maintainers more efficiently diagnose and respond to bug reports.
This exercise provides practice with
This exercise will help you gain Drupal sitebuilding/coding experience. Working on core issues introduces you to things such as the user interface, file structure, feature sets, etc. It offers a great learning experience while providing a significant service to the community. In this exercise we will start by creating a very basic issue, which is sufficient, but not ideal. Then we will test the issue, and follow up and improve the issue to make it more complete.
For more background on the issue queue, and how to correctly fill out an issue form, please read the Drupal.org documentation, Making an issue report.
There is also a short video, Getting started in the issue queue, which walks through this lesson and includes some background information on the issue queue.
Post a sample issue
Rewrite description for URL alias on node/add/*
Note: This issue is being posted here as an exercise by a participant in the http://drupalladder.org ladder for contributing to core. Please don't do anything with this post. The real issue has already been resolved in Drupal 8. If you would like to try this exercise yourself, visit http://drupalladder.org and click on Drupal Ladder
Optionally specify an alternative URL by which this content can be accessed. For example, type "about" when writing an about page. Use a relative path and don't add a trailing slash or the URL alias won't work.
The alternative URL for this content. For example, type "about" when creating an about page. Use a relative path without a trailing slash
Confirm a reported bug and improve the issue
git clone --branch 8.x https://git.drupal.org/sandbox/bhirsch/1388780.git drupal_8_sandbox_for_drupal_ladder
Update the issue summary
Contributors are strongly encouraged to use the drupal.org issue summary template, especially for posts with lots and lots of comments. Take a minute to familiarize yourself with the template and use it to re-write the issue post you just created. Under sections that are not applicable, like API Changes, just say "none." If you don't know, just say "I'm not sure." (See an exemplary issue post.)