Changes between Version 63 and Version 64 of GitPlugin


Ignore:
Timestamp:
Oct 17, 2010, 6:39:47 PM (14 years ago)
Author:
Herbert Valerio Riedel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GitPlugin

    v63 v64  
    8181== Configuration ==
    8282
    83 Simply point your Trac instance to a local git repository:
     83See also `wiki:TracIni#git-section` of your current Trac installation (if GitPlugin is enabled), for an up-to-date list of customizable `[git]` settings.
     84
     85Simply point your Trac instance to a local git repository, and configure your TracIni:
    8486{{{
    8587[trac]
     88# simple single-repository configuration
    8689repository_dir = /var/git/Test.git
    8790repository_type = git
    8891
    8992## the following settings are only supported for plugin version 0.11 or later
     93
    9094[git]
    9195## let Trac cache meta-data via CachedRepository wrapper; default: false
     
    118122}}}
    119123
     124=== Multi-Repository Configuration ===
     125
     126Starting with Trac 0.12, GitPlugin gained support for multi-repository configuration
     127(see also T:TracRepositoryAdmin for generic instructions)
     128
     129''TODO: write about current issues wrt GitPlugin and how to workaround them''
     130
    120131=== post-receive hook scripts ===
    121132
     
    123134
    124135With Trac 0.12 a VC independent plugin approach to handling ticket references in commit messages has been put into place.
    125 Thus for 0.12 in you basically need to enable the !CommitTicketUpdater component in `trac.ini` or via the webinterface under 'Admin/Plugins'. Additionally you have to call `trac-admin TRAC_ENV changeset added <commitid(s)>`, e.g. by putting a `post-receive` script into yourRepository.git/hooks/ along the lines of:
     136Thus for 0.12 in you basically need to enable the !CommitTicketUpdater component in `trac.ini` or via the webinterface under 'Admin/Plugins'. Additionally you have to call `trac-admin TRAC_ENV changeset added <commitid(s)>`, e.g. by putting a `post-receive` script into `your_repository.git/hooks/` along the lines of:
    126137{{{
    127138#!python