610 | | Yes, you can setup Subversion to update the Trac ticket when you commit changes with a message listing tickets that are fixed or related. You can read the comments in the beginning of the file contrib/trac-post-commit-hook source:/trunk/contrib/trac-post-commit-hook for more information on how to set this up. |
611 | | |
612 | | If you are using a stable version rather than the latest development version you should instead get the script which matches your release - for example source:/branches/0.9-stable/contrib/trac-post-commit-hook ('''if you build from source, you will find the correct script version in your trac-xxx/contrib folder''') |
| 610 | Yes, you can setup Subversion to update the Trac ticket when you commit changes with a message listing tickets that are fixed or related. |
| 611 | |
| 612 | ==== Trac 0.12 |
| 613 | Trac 0.12 introduced a new, more general, method to accomplish this. You can, for example, activate the optional !CommitTicketUpdater plugin that is part of Trac 0.12, and then define repository hook scripts as described [TracRepositoryAdmin#ExplicitSync here]. |
| 614 | |
| 615 | For more info about the optional !CommitTicketUpdater plugin provided by Trac, see the file tracopt/ticket/commit_updater.py source:/trunk/tracopt/ticket/commit_updater.py. |
| 616 | |
| 617 | For another example on how to relate tickets and changesets, see TracHacks:TracTicketChangesetsPlugin. |
| 618 | |
| 619 | ==== Trac 0.11 and previous versions |
| 620 | |
| 621 | If you are using a stable version prior to Trac 0.12, you should instead get the script which matches your release - for example source:/branches/0.11-stable/contrib/trac-post-commit-hook ('''if you build from source, you will find the correct script version in your trac-xxx/contrib folder''') |