Edgewall Software
Modify

Opened 15 years ago

Closed 15 years ago

Last modified 9 years ago

#7893 closed enhancement (worksforme)

trac-post-commit-hook/TracLink policy mismatch

Reported by: julien@… Owned by:
Priority: low Milestone:
Component: general Version: 0.11.2.1
Severity: minor Keywords: post-commit-hook, TracLink, traclinks
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

I just set up Trac 0.11.2.1 on my project and install the post commit hook for SVN.

Everything is working well. Thanks for all.

Client side, I use TortoiseSVN and I have defined the following properties on my trunk folder:

bugtraq:logregex
([cC]lose|[cC]losed|[cC]loses|[fF]ix|[fF]ixes|[fF]ixed|[rR]eferences|[rR]efs|[aA]ddresses|[rR]e|[sS]ee)\s+((\s*(,|and|&)?\s*)?(#|([tT]icket|[iI]ssue|[bB]ug)(\s|:)?)\d+)+
(\d+)

to suit the hook parsing convention. (Tortoise does a color highlighting in the commit log message when the regexpr match, add hyperlink and a column with ticket numbers in the show log dialog, so user-friendly.)

The fact is that TracLinks only match #<number> or ticket:<number> and not all the (#|([tT]icket|[iI]ssue|[bB]ug)(\s|:)?) possibilities so my comments have some link and other not…

Such a shame: the hook parsing and TracLinks naming convention are not the same.

Do you plan to update TracLinks ? Otherwise, reduce the hook parsing policy ? One of the two solution will give you a more integrated/consolidated project.

Best regards

Great work

Attachments (2)

screemshot.jpg (54.2 KB ) - added by julien@… 15 years ago.
Screen shot of the rendering in the auto generated comment
screenshot.jpg (44.4 KB ) - added by julien@… 15 years ago.
Screen shot of the rendering in TortoiseSVN

Download all attachments as: .zip

Change History (6)

by julien@…, 15 years ago

Attachment: screemshot.jpg added

Screen shot of the rendering in the auto generated comment

by julien@…, 15 years ago

Attachment: screenshot.jpg added

Screen shot of the rendering in TortoiseSVN

in reply to:  description ; comment:1 by Emmanuel Blot, 15 years ago

Replying to julien@…:

Otherwise, reduce the hook parsing policy ?

Commit hook scripts are located in the /contrib directory to indicate that they are not part of the Trac project. Actually, they should be considered as a base to implement your own hook scripts, depending on the way you use Trac+SVN in your team.

It should be quite straightforward to remove the extra syntax from the hook scripts so that they only accept the TracLinks format.

in reply to:  1 comment:2 by Christian Boos, 15 years ago

Milestone: 0.11-retriage
Resolution: worksforme
Status: newclosed

Replying to eblot:

It should be quite straightforward to remove the extra syntax from the hook scripts so that they only accept the TracLinks format.

Right, and there's even an example for Revision and Changeset that can be adaptaed to Issue, Bug, etc.

See source:tags/trac-0.11/sample-plugins/revision_links.py

comment:3 by Ryan J Ollos, 10 years ago

Keywords: traclink added

comment:4 by Ryan J Ollos, 10 years ago

Keywords: traclinks added; traclink removed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.