Changes between Version 8 and Version 9 of TracAndVersioning
- Timestamp:
- Feb 23, 2015, 8:07:37 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracAndVersioning
v8 v9 1 = How Trac and version control systems work together =1 = How Trac and version control systems work together 2 2 3 3 ''These examples use Subversion terminology'' 4 4 5 == Supported features ==5 == Supported features 6 6 7 I t 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.7 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. 8 8 9 == How it works ==9 == How it works 10 10 11 The integration between Trac and the version control system depends on TracLinks. Every time a change is commit ed 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 ticket11 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. 12 12 13 13 TODO: Please tell which version of Trac supports these commit hooks and if it does that automatically. … … 15 15 With additional logic in the commit hooks it is possible to reject the commit if no ticket number is supplied. 16 16 17 == Provided functions ==17 == Provided functions 18 18 19 19 * TracLinks 20 20 * TracChangeset 21 21 22 == Example 22 23 23 == Example == 24 25 1. A Trac user begins work on a ticket 26 1. They obtain code from the version control system 27 1. After the work is completed they perform a commit of their modifications to the version control repository 28 1. The user inserts the Trac ticket number into the commit message as a TracLinks 29 1. Trac can now display the change set for the ticket 24 1. A Trac user begins work on a ticket. 25 1. They obtain code from the version control system. 26 1. After the work is completed, they perform a commit of their modifications to the version control repository. 27 1. The user inserts the Trac ticket number into the commit message as a TracLinks. 28 1. Trac can now display the changeset for the ticket.
