> On May 21, 2015, at 11:46 PM, RjOllos <[email protected]> wrote: > > On Thursday, May 21, 2015 at 2:04:18 PM UTC-7, Josh Santangelo wrote: > Good that [repositories] is supported in my version of Trac, but it’s still > unclear to me what to put in there. The docs show: > > [repositories] > .type = git > .dir = /path/to/my/git/repository/.git > > Do I just repeat .type and .dir for each repository? Is something supposed to > go before the dot? > > Yes, the repository name goes before the dot. If you omit the repository > name, then you are referring to the default repository, which can also be > referred to using the notation "(default)" (for example, when using > trac-admin $env repository resync $repos -> trac-admin $env repository resync > resync "(default)”).
Gotcha. But since I’ve got the repositories configured in the database via the admin panel, specifying them in [respositories] isn’t necessary, right? > And what is the difference between [repositories] and the > /admin/versioncontrol/repository page, where I already have all of my > repositories entered? > > They are different repository data stores. You can use either, or even define > different repositories in each, though that's probably not recommended. > > I've done some work over the past few days to try and clarify the > documentation. I appreciate if you can read and suggest any areas that you > find confusing, redundant or lacking information: > http://trac.edgewall.org/wiki/1.1/TracRepositoryAdmin > <http://trac.edgewall.org/wiki/1.1/TracRepositoryAdmin> This is definitely quite a bit more clear. > > I probably wasn’t very clear — my changeset links aren’t directing to GitHub > — they’re directing to nothing at all. Here is a screenshot. > > https://www.dropbox.com/s/19i6l6t8y9aiigv/Screenshot%202015-05-21%2013.57.19.png?dl=0 > > <https://www.google.com/url?q=https%3A%2F%2Fwww.dropbox.com%2Fs%2F19i6l6t8y9aiigv%2FScreenshot%2B2015-05-21%2B13.57.19.png%3Fdl%3D0&sa=D&sntz=1&usg=AFQjCNEHJHyXIHZ3sWRSAt604RhhU3E-Jg> > > I haven’t been using a post-commit hook, I’ve been using a script which polls > my repos and calls "trac-admin env changeset added" when new commits show up. > It’s sort of janky but mostly works. > > Do you have "tracopt.ticket.commit_updater.* = enabled" in your [components] > section? Yes, that’s in there. My understanding is that’s what causes the commit comments to be added to the tickets. That’s working correctly, it’s just that the text in the comment doesn’t link to anything. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
