We need to replicate the support for issue nid hyperlinking that d.o currently has with project* in commitlog.

Comments

marvil07’s picture

marvil07 commented
Title: Add support for issue nid hyperlinking » Add support for issue nid hyperlinking based on commit
Project: Version Control API » Version Control / Project* integration
Version: 6.x-2.x-dev » 6.x-1.0-rc2
Component: Commit Log » Code

Actually, there is support to parse commit message and link based on an URL pattern set on repository configuration.

But there's still a need to make a back-link to the commit at the issue, based on commit, I'm not really sure where this code should be, so moving to project integration, since that happen on an node.

sdboyer’s picture

sdboyer commented

Love it when I find out there's already stuff in place :) I really need to take some time and comb through vc_project, though.

marvil07’s picture

marvil07 commented
Category: task » feature
Status: Active » Closed (duplicate)

Marking as a duplicate of #493074: Back-link to the commit as a comment on the related issue..

mikey_p’s picture

mikey_p commented
Status: Closed (duplicate) » Active

Re opening this as it is describing different functionality than #493074: Back-link to the commit as a comment on the related issue.. This issue is about turning any reference to an issue # in a commit message into a link. See http://drupal.org/cvs?commit=467500 for an example where the issue nid at the beginning of the issue is turned into link. I'm not sure if this should live in VC API or VC Project. If this is already in VC API, then great, I'd just like to know how to configure it, otherwise we need to figure out where it belongs.

@sdboyer, which module has the code you are referring to?

mikey_p’s picture

mikey_p commented
Version: 6.x-1.0-rc2 » 6.x-2.x-dev

Upping the version.

marvil07’s picture

marvil07 commented
Project: Version Control / Project* integration » Version Control API
Component: Code » Views integration
Category: feature » bug
Status: Active » Closed (duplicate)

Ok, if this is reffering to the regression(working on 6.x-1.x) introduced while refactoring commitlog to use views, that should be working when #976148: Recover links to VCS web viewers and issue tracker at views(after #354509: Make repository URL backends pluggable) is ready. So this would be converting into a duplicate of another issue, at VCS API.