Bugzilla – Full Text Bug Listing
| Summary: | allow commit comment templates to be set per repository | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> |
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | mauromol, steffen.pingel, stepper |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Mik Kersten
Would be nice, but not likely we can get to this by 1.0. But others should feel free to vote if lack of this is getting in the way. is this a duplicate of bug 150663 ? Yup, thanks for noticing. *** This bug has been marked as a duplicate of bug 150663 *** *** Bug 210173 has been marked as a duplicate of this bug. *** Please reconsider this. This enhancement is marked as a duplicate of bug 150663, while bug 210173 is marked as a duplicate of this. Actually, bug 150663 was asking for commit template support per project AND per task repository, but only the first part was done. This enhancement and bug 210173 are instead asking for the second part. Actually, I find it much more reasonable to have a task repository specific commit template, rather than a project specific commit template. In fact, what is usually the case is that the task repository is an issue tracker with some sort of hooking on commit comments to extract information and add it to the task. I'm thinking of Bugzilla+Scmbug, Trac SVN integration, JIRA SVN integration, etc.. Every solution has a (configurable?) pattern to detect task references within commit comments. For instance: - Scmbug detects references like "bug #nnnn" - Trac detects references like [addresses #nnnn] - JIRA detects references like PROJECT-NNNN and so on. From this point of view it would be useful to set on each task repository a specific commit comment template to use whenever I'm committing a changeset related to a task in that repository. I do not find it useful to have a project specific commit template, simply because in our case we're tracking different type of issues on the same project with different issue trackers (i.e.: user reported bugs with Bugzilla, internal project lifecycle related tasks with Trac, etc.): so we can't identify a commit template for the whole project, but we would need one for each task repository. As for the templates precedence, I think this would be reasonable: - if a project specific template is defined, use that - otherwise, if a task repository specific template is defined, use that - otherwise use the workspace defined template as a fallback So, please consider reopening this enhancement request. |