= How Trac and version control systems work together

''These examples use Subversion terminology''

== Supported features

Identifying the revisions and modifications that were made to complete a change allows users and developers which modifications were made for a ticket. Such an identification is called a TracChangeset.

== How it works

The integration between Trac and the version control system depends on TracLinks. Every time a change is committed to the version control repository, a TracLink must be used in the comment (usually referred to as a commit message) that includes a reference to the correct ticket.

TODO: Please tell which version of Trac supports these commit hooks and if it does that automatically.

With additional logic in the commit hooks it is possible to reject the commit if no ticket number is supplied.

== Provided functions

 * TracLinks
 * TracChangeset

== Example

 1. A Trac user begins work on a ticket.
 1. They obtain code from the version control system.
 1. After the work is completed, they perform a commit of their modifications to the version control repository.
 1. The user inserts the Trac ticket number into the commit message as a TracLinks.
 1. Trac can now display the changeset for the ticket.