On Fri, May 13, 2016 at 12:58 PM, Warren Young <w...@etr-usa.com> wrote: > > We aren’t talking about fossil ui. We’re talking about > > $ f ci -m “closes [12345abc]” > > Under your scheme, that would run a TH1 commit hook. So: does an HTTP > call made from fossil ci send a suitable cookie to tell the remote fossil > server on autosync that it is user foo, so it should let it close ticket > [12345abc]?
I did not claim my scheme would work for a remote Fossil server. I've only been answering your questions as you've made them. Ideally, the set of commands available to TH1 hook scripts could be expanded to include things like adding/updating tags and updating tickets. Alternately, the capability to spawn a program (or a shell to run a script). Maybe those things can be done (mostly) in SQL via TH1's query command, but doing so would require crafting code to create various artifacts to be inserted into the blob table. I don't know how dificult that would be.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
