Add link to patch creation/application handbook page on issues with patches
| Project: | Drupal.org infrastructure |
| Component: | Drupal.org module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | drupal.org redesign |
Jump to:
One of the main barriers to involvement in the Drupal community is of course lack of knowledge about specific procedures. This suggested tweak to the issue pages would put needed information at the fingertips of anyone interested in testing a patch.
(Real motivation: I'm dyslexic and have to look up which way the < angle bracket goes every time.)
The help text could be added as an extra block in the sidebar (user-configurable but on by default) or as text added directly to the comment or to the new top-right "Jump to" navigation links ("Most Recent Comment, Most Recent Attachment...") for any issue that has the status "patch (code needs review)". Perhaps it should also check if there is a file attached.
The help text would be "How to apply a patch" and link to http://drupal.org/node/60108 (or perhaps to a page that combines key elements of that "Applying patches" page and "Reviewing patches," http://drupal.org/patch/review
(Also: Perhaps all issues should have a link to http://drupal.org/patch/create and/or http://drupal.org/patch/submit )
I'd be happy to code a simple module (or patch drupal.org module) to do this, with some feedback on the approach to take, and if anyone can point to where the "Jump to" links are implemented that would be very helpful.
benjamin, Agaric Design Collective
#1
I think something like this would be a good idea, but I'm not sure about this approach. Take a look at my recent comment #64220-9: Hyperlink issue metadata values which, if implemented, would be a more robust solution, in my opinion. I might recommend seeing if we can come to a consensus there first, and if that consensus would solve your problem here we can just fix this in the project issue tracking module. But if you don't like that idea, I'm happy to discuss how to do this here also, though I can't make the call on what should actually be implemented on drupal.org.
These are created in the issue.inc file in the project_issue_internal_links() function. I don't think the drupal.org module could override these, however. It should be possible to add an additional link to the $summary_links array by overriding theme_project_issue_summary() on d.o, but that might be a bit hackish.
#2
Rewriting title to make this a bit more general. Also, #241851: Add "learn how to test this patch" on project-issue followups was marked a duplicate of this issue.
#3
subscribe
#4
I'd second this request.
#5
Tagging for "Drupal.org redesign", and unassigning from myself until I get up to speed on the modern Project module.