On May 12, 2016, at 2:07 PM, Ron W <ronw.m...@gmail.com> wrote: > > On Wed, May 11, 2016 at 7:29 PM, Warren Young <w...@etr-usa.com> wrote: > On May 11, 2016, at 3:57 PM, Marko Käning <sec001+fos...@posteo.net> wrote: > > > > An auto-closing of tickets if the commit comment contains stg like "closed > > [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]", > > would be nice. > > it might be possible to do this with a TH1 commit hook script. TH1 has a http > command, so you can build an HTTP post request to trigger a web service.
Where would it get the user credentials for that? Modifying tickets is not allowed for anonymous. No, you’d have to call one of the internal Fossil APIs exported by Fossil, so that it would use the committer’s credentials. > I've never used Fossil's TH1 hooks, so I don't know much about them. The main thing to know about them is that they aren’t enabled by default, and you have to write their code manually. That makes them good for things that are entirely site-specific. Thus, TH1 hooks might be a good way to prototype the behavior of this feature prior to implementing it, but in the end, we’d want something in the core that works everywhere, out of the box. I don’t really see a need to prototype it, though, because this is a fairly common thing in other VCS + bug tracker integrations. The fact that Fossil has both in the same package but doesn’t have this typical behavior built in is what surprises so many. > TH1 also has a query command that runs an SQL expression. That would be a valid argument for prototyping the feature in TH1: if the C implementation will involve some intricate SQL, it might be nice to prototype it in an interpreted language that doesn’t require rebuilding Fossil for each attempt. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
