Edgewall Software

Version 3 (modified by Bruce Christensen <trac@…>, 18 years ago) ( diff )

Copyediting

How Trac and version control systems work together

These examples use Subversion terminology

Supported features

It is useful to identify the revisions and modifications that were made to complete the change. This is called a TracChangeset and allows users to clearly identify which modifications were made for a ticket.

How it works

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

With additonal logic in the commit hooks (using Subversion terminology) it is possible to reject the commit if no ticket number is supplied.

Provided functions

Example

  1. A Trac link user begins work on a ticket
  2. They obtain code from the version control system
  3. After the work is completed they perform a commit of their modifications to the version control repository
  4. The user inserts the Trac ticket number into the commit message as a TracLinks
  5. Trac can now display the change set for the ticket
Note: See TracWiki for help on using the wiki.