OK, I've Googled, browsed endless FAQs, and scratched my head to no end. Now it's time to ask for help.
We're using Mercurial for source control, Review Board for code reviews, and Trac for ticketing. So far, everything's working ... except for one feature. When I used Trac with Subversion, I loved the ability to see commit messages and changeset references in my tickets. Knowing that a commit could update and close a ticket made my workflow smoother and kept all the developers happy. But I can't seem to do that with Mercurial. Yes, Trac can see all of my repositories, and I can browse the code and revision history just as I'd expect. But if I commit (and push) a changeset that references a Ticket ... nothing. Example: Rev: @31:80bfbcfe2bbe Message: Fix a spacing issue - see #4. In the revision log, #4 links to my ticket as I'd expect, but nothing shows up in the ticket! I went through and enabled the CommitTicketUpdater component, but I'm still not seeing anything. I've seen other references to post-commit hooks, but this is where I'm stuck. Do I put these post-commit hooks in my local clone of the repository or in the central repository on the development server? I can't see how they'd work on the server, because it's not actually committing anything. But I can't see how they'd work locally because I don't have local access to `trac-admin` on the server. Do I even need these hooks? Maybe I've messed something up somewhere else. So, what do I need to do such that commits/pushes that reference tickets are automatically added to the ticket using TracMercurial? -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
