On Wed, May 18, 2016 at 2:12 PM, Steve Schow <st...@bstage.com> wrote: > > I’m going to try to make some kind of wrapper script to my commit command > that can do this for me, but before I embark I am wondering if anyone has > thought of any good ways to do this, perhaps using TH1 in the repo or > something….or perhaps using the checkout DB in some way to keep track of > what the current ticket is. >
While TH1 has a query function to process SQL expressions in a TH1 script, only the ticket hook script would be able to access the check out DB an donly when triggered by a "fossil ticket" command line command. Even then, I don't know if you'd have access to the check out DB. A wrapper script might be able to use "fossil sql" command line commands to store and retrieve info in the check out DB. I've never tried it. The SQLite project has a command line client that could be used to store and retrieve info in the check out DB. My personal solution to this is to set the Fossil "editor" option to run a script that launches my preferred text editor with the previous commit message preloaded. Then I just edit what needs to be edited, save and quite the editor. Then the script copies the message to the temporary file supplied by Fossil.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
