| | 1 | = Commit Ticket Updater = |
| | 2 | |
| | 3 | The Commit Ticket Updater is an **optional component** which makes Trac react on keywords and ticket references found in commit log message. Referenced tickets get a new comment linking to the changeset and depending on the presence of appropriate keywords (like //closed//, //fixed//, //reopened//, etc.) the ticket status will be updated. |
| | 4 | |
| | 5 | That role was fulfilled by the [source:branches/0.11-stable/trac-post-commit-hook trac-post-commit-hook] for Subversion and previous versions of Trac (up to 0.11), but starting with Trac 0.12 and [TracRepositoryAdmin multiple repository support], a more general notification solution has been adopted. |
| | 6 | |
| | 7 | The post-commit hooks now should simply use `trac-admin` to notify the TracEnvironment that a changeset has been |
| | 8 | //[[span(title=trac-admin <env> changeset added <repos> <rev>,added)]]// or |
| | 9 | //[[span(title=trac-admin <env> changeset added <repos> <rev>,modified)]]//. See TracRepositoryAdmin#ExplicitSync for more details. |
| | 10 | This works for any kind of VersionControlSystem supported by Trac and can notify that information to any kind of listener, not only the commit ticket updater (see [[TracDev/ApiChanges/0.12#IRepositoryChangeListener]]). |
| | 11 | |
| | 12 | The `CommitTicketUpdater` component lives in source:trunk/tracopt/ticket/commit_updater.py and is maintained alongside the Trac core. As its rooted in the `tracopt.` packages and not in `trac.`, it's not turned on by default and therefore needs to be explicitly activated. See the tip in TracRepositoryAdmin#trac-post-commit-hook. |
| | 13 | |
| | 14 | |
| | 15 | |
