Modify ↓
Opened 16 years ago
Closed 16 years ago
#6395 closed enhancement (wontfix)
trac-post-commit-hook also logging greatest common folder
| Reported by: | Owned by: | Jonas Borgström | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Hi
I keep a ticket to log all merges to trunk. It would be nice if the trac-post-commit-hook also could log the greatest common folder for a changeset to be able to see from which branch a merge originated.
When using the current trac-post-commit-hook something like this is logged in trac:
(In [19096]) addresses #NNNN bla bla
With the attached patch it will look like:
/releases/branches/branchA/component (In [19096]) addresses #NNNN bla bla
Attachments (1)
Change History (2)
by , 16 years ago
| Attachment: | log_common_dir.diff added |
|---|
comment:1 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The commit hooks are provided as examples to help users write their own hooks and tailor them to their needs, this is one of the reason why the hooks are kept in the contrib/ directory.
Closing as wontfix, people willing to use this extra feature can download and apply your patch to their hooks.
Note:
See TracTickets
for help on using tickets.
Adds greatest common folder to the trac log